Bundleport Hotel Content API
REST API for static and semi-static hotel catalog data: hotels, destinations, rooms, boards,
categories, metadata, and scope audit/stats. Public paths are under /content/hotels/v1/....
Related docs: Static vs transactional data, Booking API.
Live availability and booking use the Hotels (aggregator) API, not this service.
Health: GET /content/hotels/v1/health (no auth). Other routes require authentication via API key / bearer token as configured for your environment.
Provider codes and families. A few providers answer to more than one code, because content and mappings were onboarded under different names. Send the code you were given. The API resolves aliases to the same family before querying. Responses report the code as stored, so a request using one alias can come back labelled with the other in mapping-related fields.
Try it: Default servers are production and test gateways; paths already include /content/hotels/v1/.... Use sk_test_* with the test host.
Authentication
- HTTP: Bearer Auth
- API Key: apiKeyAuth
Gateway JWT after Authorization: ApiKey sk_* is exchanged, or a Clerk Bearer token.
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | JWT |
Buyer header ApiKey sk_test_* or ApiKey sk_prod_*. Do not send X-API-Key.
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | Authorization |
Contact
Bundleport Team: