API Reference overview
The REST API documentation is split into two OpenAPI references that match how the product is deployed:
| Reference | Role | Public gateway prefix |
|---|---|---|
| Booking API | Live search, quote, book, list, detail, cancel | https://api.bundleport.com/connect/hotels/v1/... (test: https://test-api.bundleport.com/...) |
| Content API | Static / semi-static catalog (hotels, rooms, destinations, boards, categories) | https://api.bundleport.com/content/hotels/v1/... |
Use the Content API to power filters, hotel detail pages, and code lists. Use the Booking API for anything that depends on supplier inventory or price right now. The conceptual split is explained in Key concepts — Static vs transactional.
Authentication and environments
- Header:
Authorization: ApiKey <your-key>(see Authentication). - Test keys (
sk_test_*) →test-api.bundleport.com. Production keys (sk_prod_*) →api.bundleport.com.
Machine-readable OpenAPI
Stable YAML for generators, Postman, and IDEs (copied from the specs that drive this site):
- Booking:
https://docs.bundleport.com/openapi/hotels.yaml - Content:
https://docs.bundleport.com/openapi/content.yaml
Contract card · Use with AI · llms.txt
OpenAPI — generate the client
Stable YAML for OpenAPI Generator, Postman, Insomnia, and IDE plugins. Import the file; do not install unpublished SDK packages.
llms-full.txthttps://docs.bundleport.com/llms-full.txt
Product documentation vs OpenAPI pages
- Narrative guides (flows, best practices, examples): Connect Hotels overview, Quickstart, Guides.
- OpenAPI pages (every path, schema, and Try it): use the sidebars on each reference, or the links above.
Other interfaces
MCP is documented under Alternative interfaces in the main sidebar; it exposes the same capabilities as the Booking API through a tool-based transport.