Docs
Get an API key
Hotel webhooks

List your subscriptions

GET
/v1/hotel/webhook-subscriptions

You receive your organization's subscriptions, oldest first, without their signing secrets.

Authorization

x-api-key<token>

Your API key. Issued and revoked from the TrustPixel dashboard; the gateway resolves it to an owning organization on every request.

In: header

Header Parameters

x-request-id?string

Correlation id echoed to the upstream service and returned on the response. Generated as req_<uuid> when omitted.

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/v1/hotel/webhook-subscriptions"
{  "data": [    {      "id": "string",      "url": "string",      "event_types": [        "hotel.booking.confirmed"      ],      "status": "ACTIVE",      "previous_secret_expires_at": "2019-08-24T14:15:22Z",      "created_at": "2019-08-24T14:15:22Z",      "updated_at": "2019-08-24T14:15:22Z"    }  ]}

List your hotel bookings GET

You receive your booking summaries from newest to oldest, each with its payments but without their cards. You filter by status, your exact reference_id, or both; these filters apply only to bookings owned by your organization and user. A reference is not unique, so keep every matching result. Use limit and offset to request another page with the same filters, and stop when meta.has_more is false. Concurrent changes can shift offset-based pages. Read a booking by ID for its contact, room details and cards.

Create a subscription POST

You register an HTTPS endpoint and the events it receives. You receive the signing secret only in this response; store it on your server. Your organization holds at most five subscriptions, one per URL, shared by all its credentials.