This API has been deprecated.
Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.
Learn more in the API Lifecycle & Deprecation Policy.
The Hotel Services Direct Connect from Concur Connect provides a method for Travel users to access hotel inventory.
Once the hotel supplier has developed and certified their interface with Concur, their inventory will begin appearing in hotel searches by opted-in Travel users.
This callout differs from the inbound Concur web services in the following ways:
This direct connect is only available to Travel Suppliers with Hotel inventory. This direct connect is not supported in the Concur mobile application.
Concur products are highly configurable, and not all clients will have access to all features.
Partner developers must determine which configurations are required for their solution prior to the application review process.
The configuration process has the following steps:
Once the configuration is complete, the callout uses the following process:
This callout can also be used to perform the following functions:
The hotel direct connect sends the relevant information to a URL that the travel supplier maintains.
A recommended URL structure is:
The URL is provided by the supplier when registering the partner application.
You can use either one endpoint for all messages, or a dedicated one for each message type. In that case you have to follow these rules:
The only allowed difference between the endpoint URLs can be the message name (without OTA_ and RQ/RS):
The variable part doesn’t need to be at the end:
Concur will make calls to the application connector’s endpoint using SSL. During configuration, Concur will connect to the application connector to validate that its hostname and access credentials are valid.
Concur will not be able to connect to the application connector until a certificate signed by a Certificate Authority (CA) is installed in the application connector. If you are hosting the application connector, you will need to install the signed certificate before Concur can access the connector.
Concur will use Http Basic authentication. The hotel supplier will need to provide credentials that Concur will send to the supplier’s system for each message.
The Concur outbound message format is based upon a subset of the OTA2011B hotel standard. Please refer to the Function links below for the details of the request and response format.
Please note the following general information about this format:
The Travel clients opt in to the Hotel inventory using a setting in the Travel Configuration. Clients must contact Concur to have this setting activated.
In most cases, new versions of Hotel Services will involve adding support for various optional nodes and attributes in the OTA standards. These changes will be backwards compatible and should not require any mandatory changes and hotel suppliers will be upgrade automatically. In the situation where a change is implemented which cannot be made backwards compatible, suppliers will need to upgrade the Hotel Services interface by and provide a new set of hotel URIs. Concur recommends that the version of the interface be part of the hotel URI provided by the hotel suppliers.
The certification process will start once the vendor has completed their integration with the Concur certification systems. Certification consists of running through several use cases on the certification servers and validating that in each scenario the correct response is sent. Typically, most potential issues are being worked out during the integration process and certification can be accomplished in a day or two. An example of a use case during certification would be a user searching and booking a property several months out, viewing an itinerary, changing the dates of the property, and then cancelling the reservation.
For error handling we don’t use any special message. Just return the appropriate response, only replace Success node with Errors and provide some error description. Please follow the OTA Code Table for error codes. Please provide as descriptive error text as possible. It will make tracing problems lot easier on both sides.
Information on format or value requirements that are used in multiple endpoints is included here.
All the codes used by the Hotel Direct Connect are documented in the Hotel Direct Connect Code PDF.
The corporate identifier will be passed as RequestorID node. The values will be configured on setup. Please keep the Type compliant with ID Type Codes.
<POS> <Source ISOCountry="US" ISOCurrency="USD"> <RequestorID Type="4" ID="7777777" ID_Context="MyHotel" /> </Source> </POS>
If a vendor requires additional identification of the client system (all calls to vendor will have the same value), you can provide a second RequestorID:
<POS> <Source ISOCountry="US" ISOCurrency="USD"> <RequestorID Type="4" ID="7777777" ID_Context="MyHotel" /> <RequestorID Type="7" ID="8172927" ID_Context="WholeTravel" /> </Source> </POS>
Please keep the Type compliant with ID Type Codes. The supported codes for the Requestor ID Type are: 1,2,3,4,5,7,9,13,18,21
ID Type Codes Table
|2||CRO (Customer Reservations Office)|
|26||Associated itinerary reservation|
|27||Associated shared reservation|
|35||Purged master reference|