Hotel API Endpoints

This topic provides a consolidated list of endpoints and associated methods for all Hotel APIs. For links to all topics see the Hotel API Reference List.

In this topic:

• Authentication
• Base Path for all Hotel APIs
• JSON Hotel API Endpoints List

Authentication

All Travelport JSON APIs require authentication with OAuth 2.0. Before calling any API, you must follow an OAuth-based authorization procedure to obtain an access token. That access token is valid for 24 hours and must be sent with every call during that time. Do not request a new token for each API call. See Authentication for full details.

Use these endpoints for authentication requests:

Pre-production https://auth.pp.travelport.net/oauth/token

Production https://auth.travelport.net/oauth/token

Base Path for All Hotel APIs

Every JSON API requires a request sent to an authorization endpoint unique to that API. This unique endpoint is listed at the top of every API Reference in this online help. In addition, this topic provides a consolidated list of all endpoints.

The beginning string of these endpoints are the same across all Hotel APIs on the same major model version, and is called a base path because it is shared across APIs. The following are the current, post-migration base paths for the JSON v11 and v12 Hotel API endpoints.

Base path for v11 APIs:

Pre-production https://api.pp.travelport.net/11/hotel/

Production https://api.travelport.net/11/hotel/

Base path for v12 APIs:

Pre-production https://api.pp.travelport.net/12/hotel/

Production https://api.travelport.net/12/hotel/

Combine the appropriate base path with the Hotel API authorization endpoints in the next section. For example, the complete post-migration endpoint for the Hotel Availability API in the production environment is

https://api.travelport.net/11/hotel/availability/catalogofferingshospitality

JSON Hotel API Endpoints

The following tables lists the endpoint for each Hotel API and links to the corresponding API reference. All APIs are v11 unless noted as v12 (what's the difference?). The endpoint includes any required query parameters.

Request	Endpoint (add to Base Path above)
Search by ID	POST search/properties
Search by Location	POST search/properties/search
Search Pagination	GET search/properties/{SearchIdentifier}?pageNumber={x}
SearchComplete (v12)	POST search/searchcomplete/
SearchComplete Pagination (v12)	GET search/searchcomplete/{SearchIdentifier}?pageNumber={x}
Hotel Details	GET search/propertiesdetail?chainCode={xy}&propertyCode={12345}
Hotel Availability	POST availability/catalogofferingshospitality
Hotel Availability Pagination	POST availability/catalogofferingshospitality/{SearchIdentifier}?pageNumber={x}
Hotel Rules (full payload)	POST rules/offershospitality/buildfromrequest
Hotel Rules (reference payload)	POST rules/offershospitality/buildfromcatalogoffering
Create Reservation (full payload)	POST book/reservations
Create Reservation (reference payload)	POST book/reservations/build
Retrieve hotel reservation	GET book/reservations/{AggregatorLocatorCode}
Modify hotel reservation	PUT book/reservations/{AggregatorLocatorCode}
Cancel hotel reservation	PUT book/reservations/{AggregatorLocatorCode}/canceloffer?supplierLocator={SupplierLocatorCode}
Add reservation to existing reservation (full payload and reference payload use the same endpoint)	PUT book/reservations/{AggregatorLocatorCode}
Create passive hotel reservation	POST book/reservations/passive
Add passive hotel reservation to existing reservation	PUT book/reservations/{AggregatorLocatorCode}/passive
Modify passive hotel reservation	PUT book/reservations/{AggregatorLocatorCode}/passiveupdate
Sync hotel reservation	POST book/reservations/