Skip to main content

HotelX Endpoint

Travelgate uses different GraphQL hosts depending on the type of operation you are making.

Operation typeEndpointPlaygroundTypical calls
Shopping and booking flowhttps://api-shopping.travelgate.com/graphqlShopping API Playgroundsearch, quote, book, cancel, booking, amendments, oneStepBook, oneStepQuote
Content and static master datahttps://api-content.travelgate.com/graphqlContent API Playgroundhotels, boards, destinations, chains, rooms
Shared / generic GraphQLhttps://api.travelgate.comShared API Playgroundstats, 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/graphql for any HotelX shopping or reservation workflow.
  • Use https://api-content.travelgate.com/graphql for hotel and static content queries.
  • Use https://api.travelgate.com only 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.