HTTP headers
HTTP headers are slightly different between a request made to Product API and responses returned.
Request headers
| Header | Type | Required | Input Format |
|---|---|---|---|
Authorization | String | Required | Authorization: Basic [username:password encoded by Base64] |
Content-Type | String | Required* | Content-Type: application/vnd.expedia.eps.product-v2+json For room-level actions (except for the /amenities and /rateThresholds endpoints), Content-Type is application/vnd.expedia.eps.product-v3+json |
Accept | String | Required | Accept: application/vnd.expedia.eps.product-v2+json For room-level actions (except for the /amenities and /rateThresholds endpoints), Accept header is application/vnd.expedia.eps.product-v3+json |
Request-ID | String | Optional | Can be provided and be referenced later on for troubleshooting purposes. When provided, it can be anything, and no validations will be performed to ensure uniqueness of this ID. If it is not provided in request, API will generate a UUID and return it in the response. |
*required for create and modify requests only
Response headers
| Header | Type | Format |
|---|---|---|
Content-Type | String | Content-Type: application/vnd.expedia.eps.product-v2+json For room-level actions (except for the /amenities and /rateThresholds endpoints), Content-Type is application/vnd.expedia.eps.product-v3+json |
Request-ID | String | Partner-provided request identifier. If it was not provided in the request, Expedia will generate a Request-ID and return it in the response |
Transaction-ID | GUID | Unique transaction ID generated by Expedia Group for all messages. Expedia Group recommends storing this identifier. Can be used to reference messages when troubleshooting with Expedia Group |
Location | String | Location: {url} This header is only returned from create (POST) requests and contains the full URL to the newly created resource |