Content Services for Lodging: API Support
Postman & SOAP UI collections
Postman and SOAP UI collections have been created for Content Services for Lodging (CSL) APIs to enable you to quickly get familiar with the different ways to make requests for content. Links to download these collections are shown below:
|Collection||Version 2||Version 3 (new)|
When using the SOAP/XML version of the Content Services for Lodging APIs, please note that the numbers in the namespaces will change from time to time as new functionality is released. We recommend API clients to not hard-code namespace tags to ensure their application does not break when changes are made.
API reference data / values
A list of all the reference data/codes used in the CSL APIs can be found here.
Global ID to Sabre ID Property mapping list
A list of all current properties available in CSL APIs, including Global ID to Sabre ID property mapping, can be found here.
A list of all current properties with Sabre GDS property IDs only, including Global ID to Sabre ID property mapping, can be found here.
For the CERT (the non-production) environment, we suggest to utilizing these properties for testing.
This property list is updated frequently, but to ensure access to the latest content, refer to the Resource tab on the corresponding API's page.
CSL API header format
A Customer App ID (
CustomerAppId) is optional but recommended in the header for each Content Services for Lodging API request. Individual App IDs can be requested through your Sabre Account Manager when your Shopping/Booking tool is ready to go to production.
Include the following header:
<eb:CustomerAppId xmlns:ns10="http://webservices.sabre.com/">[[Application ID]]</eb:CustomerAppId>
Individual APP IDs can be requested through your Sabre Account Manager when your Shopping/Booking tool is ready to go to production.
Note: If you encounter an error when sending a request similar to
Service [Service Name]not found with
code="ERR.NGHP-DISTRIBUTION.SERVICE_NOT_FOUND", check the Header message and ensure it DOES NOT have
<Service>[ServiceName]</eb:Service>in the request; only the
<Action>is required in the header.
Include the following in the header (key value pair) – note the dash (-) between
Application-ID [[Application ID]]
Common error messages
A list of common error messages and their meaning can be found below:
|Error||Meaning / Action|
||Security token is invalid / expired. Create a new security token using
||API access issue. Please contact firstname.lastname@example.org to request access to this API|
||Request is for aggregator content but no aggregator credentials exist. Use Hotel Manager to add aggregator credentials.|