Read supported hotel features and limits
You receive the active, configured suppliers and the features this service implements for each. Use these limits to prepare your requests; the list is shared across organizations and does not select a supplier or describe your routing rules. Read search meta.supplier to identify the supplier used for your stay. Availability, rate restrictions and booking state still determine whether a particular request succeeds. An empty list means no active configured supplier is registered. This read makes no supplier requests and is not a health check; supplier status can change after you read it.
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
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/capabilities"{ "data": [ { "supplier": "LITEAPI", "operations": [ "search", "offers", "content", "price_calendar", "prebook", "book", "cancel" ], "limits": { "max_offer_hotels": 10, "max_rooms": 8, "max_child_age": 17 }, "requires_named_adults": false, "cancellation_may_partially_succeed": false } ]}Replay a delivery POST
You send the same event again with a fresh signature. You can replay a delivered or failed delivery, a delivery pending for more than one minute, or one published more than 2 hours 15 minutes ago without a result. Your subscription must be active. Your endpoint can receive the event again, so ignore repeats by event ID.
Get flight offers POST
Price fares for a party and an itinerary. One routed supplier answers; name `supplier` to choose it yourself, and read `meta.supplier` to see who priced the fares. Offers are not stored: prebook from an `offer_reference` before its `expires_at`. `limit` caps the fares returned, and `meta.truncated` appears when more matched.