Skip to main content

CSL API Support

Postman & SOAP UI Collections

Postman and SOAP UI collections enable you to quickly get familiar with the different ways to make Content Services for Lodging requests. Links to download these collections are shown below: 

Collection Version 2 Version 3 Version 5
Postman REST
Postman SOAP SOAP SOAP
SOAP UI SOAP

Important! 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 and 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 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.

Master Chain and Affiliate Chain Lists

Master Chain qualifier groups are a family of hotel chains that are part of a single brand. This enables you to shop multiple chains that are under the same family of brands as one Master code. Similarly, Affiliate Chain codes help you keep up with a hotel group’s newest, and perhaps unknown, affiliated brands. Some chain codes serve as the primary chain and Sabre automatically appends affiliated chain(s).

For example, shopping on Radisson’s RD chain and Sabre also returns the new Quorvus Collection QC chain, if it’s a market where both RD and QC have properties. Affiliate Chain codes are especially helpful when the chains have a complementary geographic coverage and very little overlap in markets.

A list of all current master and affiliate chains can be found here.

CSL API Header Format

SOAP

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.

REST

Include the following in the header (key value pair) – note the dash (-) between Application and ID:

Application-ID                    [[Application ID]]

Common Error Messages

A list of common error messages and their meaning can be found below:

Error Meaning / Action
USG_INVALID_SECURITY_TOKEN Security token is invalid / expired.  Create a new security token using _SessionCreateRQ_.
USG_SECURITY_ICE_ERROR API access issue.  Please contact webservices.support@sabre.com to request access to this API
ERR.NGHP-AGGREGATOR.VAULT_API_ERROR Request is for aggregator content but no aggregator credentials exist. Use Hotel Manager to add aggregator credentials.