The Distribution API uses event notifications (delivered via HTTP webhooks) to inform partners about important changes, such as booking updates or venue visibility changes.
This page explains how events are delivered and how to consume them. For detailed event payloads and schemas, see the API Reference → Webhooks section.
An event represents a state change or business update within the MeetingPackage platform that may be relevant to your integration.
Examples include:
- An order / booking being created, updated, or cancelled
- A venue becoming visible or hidden for a partner
Each event is delivered as an HTTP POST request to a partner-provided endpoint.
- Events are delivered as HTTP POST requests
- Payloads are JSON (
application/json) - Events are sent to a partner-provided endpoint
Events should be treated as best-effort notifications. Integrations must tolerate missed, duplicated, or out-of-order events and use API retrieval endpoints to confirm current state when required.
⚠️ Do not rely on events alone as the source of truth. Events indicate that something changed; API retrieval endpoints should be used to confirm current state.
Event authentication is configured per partner during onboarding. Depending on the integration, this may include request headers, shared secrets, or network-level controls.
Your MeetingPackage technical contact will confirm the setup for your integration.
Event payload schemas and example structures are documented in the API Reference under the Webhooks tag.
Each event payload includes identifiers that can be used to retrieve the latest state using the appropriate API endpoints (for example, booking or RFP retrieval).
Your endpoint should respond with a 2xx HTTP status code to acknowledge receipt.
Non-2xx responses may result in the event being dropped or retried, depending on configuration. Partners should not rely on retries as a delivery guarantee.
- Review available events in API Reference → Webhooks
- Follow the RFP workflow guide for end-to-end integration examples