This page explains how webhook subscriptions are structured, how you can control which events to receive, and how delivery to your endpoints works.
Spotnana supports two ways to configure webhook subscriptions depending on how your system is set up.
Each customer organization has its own dedicated webhook subscription with a separate endpoint URL and authentication credentials. Spotnana delivers events for that organization exclusively to the configured endpoint.
This model is a good fit for partners who manage distinct integrations per customer.
Note: While our platform supports this subscription model we do not prefer this approach as it requires manual setup for each organization. We recommend using option B instead.
One webhook subscription that covers all of your customers. Spotnana delivers all events across all organizations to a single endpoint, and you route them internally based on the organization identifier (i.e., an organizationId) included in every payload.
This is the recommended model for partners integrating across multiple customers. It is easier to scale, gives you full control over your endpoint and monitoring, and reduces the overhead of managing multiple subscriptions.
Partners can choose which event and operations that they wish to receive. You can:
- Subscribe to only specific webhook events (e.g., PNR_V3).
- Filter by specific organizations using the
audience.organizationIdfield in the payload. - Exclude specific operation types within a webhook (e.g., subscribe to PNR_V3 but exclude
SCHEDULE_CHANGEoperation).
Note: Currently the operation filtering is implemented as a blacklist (i.e., to exclude specific operations that you don't want to receive).
Here are some important points to note regarding webhook delivery:
- Webhooks support payload delivery to one endpoint per subscription.
- The same message cannot be delivered to multiple endpoints from a single subscription.
- Multiple delivery subscriptions can be configured upon request if needed.