Attention: Please check the Hotel Release Notes page for the latest updates and enhancements.
Common Hotel API Headers
The table below details the common header parameters that must be included in all Hotel API requests.
| Parameter | Description | Required/Optional |
|---|---|---|
|
Accept-Encoding |
Send with the value gzip, deflate |
Required |
|
Cache-Control |
Send with the value no-cache |
Required |
|
Accept |
Send with the value application/json |
Required |
|
Content-Type |
Send with the value application/json |
Required |
|
Authorization |
Send with the value Bearer {token} See Authentication for instructions on generating the OAuth token. The OAuth token is valid for 24 hours and must be re-requested after that time. A space is required between Bearer and the token code.
|
Required |
|
XAUTH_TRAVELPORT_ACCESSGROUP |
Access group specific for each customer supplied by Travelport during provisioning. See Authentication for details on access groups. |
Required |
|
E2ETrackingID |
Optional parameter to send with any custom value of your choice to be used to track requests in the Travelport logs. This tracking ID can be helpful in the event of a support request. If you include this parameter, the value is returned in the response and may have additional characters appended to it. If you do not include this ID in the headers, the Travelport system generates one in the response in a format similar to this:
|
Optional |
|
username |
Alphanumeric username supplied by Travelport during provisioning. |
Required |
|
password |
Alphanumeric password supplied by Travelport during provisioning. |
Required |
|
client_id |
Alphanumeric client ID supplied by Travelport during provisioning. |
Required |
|
client_secret |
Alphanumeric client secret supplied by Travelport during provisioning. |
Required |