HotelX Endpoint
Travelgate uses different GraphQL hosts depending on the type of operation you are making.
| Operation type | Endpoint | Playground | Typical calls |
|---|---|---|---|
| Shopping and booking flow | https://api-shopping.travelgate.com/graphql | Shopping API Playground | search, quote, book, cancel, booking, amendments, oneStepBook, oneStepQuote |
| Content and static master data | https://api-content.travelgate.com/graphql | Content API Playground | hotels, boards, destinations, chains, rooms |
| Shared / generic GraphQL | https://api.travelgate.com | Shared API Playground | stats, logging, admin and other shared operations |
The shared API Playground currently exposes the admin, content, inventory, and booking-flow schemas. It is expected to expose only the admin operations schema in the future. Use the product-specific Playgrounds above to explore the booking-flow and content schemas.
Which host should I use?β
- Use
https://api-shopping.travelgate.com/graphqlfor any HotelX shopping or reservation workflow. - Use
https://api-content.travelgate.com/graphqlfor hotel and static content queries. - Use
https://api.travelgate.comonly for shared GraphQL operations outside the HotelX shopping/content flow.
Quick examplesβ
- Searching availability:
https://api-shopping.travelgate.com/graphql - Getting hotel or board lists:
https://api-content.travelgate.com/graphql - Reading stats or admin data:
https://api.travelgate.com
This separation keeps each API domain focused and avoids mixing shopping, content, and administrative calls on the same host.