Docs
Get an API key
Hotel price calendar

See a daily price index for your hotels

POST
/v1/hotel/price-calendar

You read a daily price index for up to 50 hotel IDs from one supplier over a window of up to 365 days: for each calendar day, the average nightly price across the stays the supplier has seen that include that day. It is not the price of checking in on that day, so present it as a trend, such as when a hotel tends to be cheaper, rather than as a price per check-in date. The prices are indicative, in US dollars, not tied to your party and not bookable, so price the stay with offers before you book. Dates without a price are omitted, and so are hotels without any. Only some suppliers publish these prices; for the others you receive 422 supplier_operation_unsupported. The supplier allows only a few of these reads a minute, so cache what you receive and expect 503 supplier_rate_limited when the limit is reached.

Authorization

x-api-key<token>

Your API key. Issued and revoked from the TrustPixel dashboard; the gateway resolves it to an owning organization on every request.

In: header

Header Parameters

x-request-id?string

Correlation id echoed to the upstream service and returned on the response. Generated as req_<uuid> when omitted.

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/v1/hotel/price-calendar" \  -H "Content-Type: application/json" \  -d '{    "hotel_ids": [      "string"    ],    "from": "2019-08-24",    "to": "2019-08-24"  }'
{  "data": [    {      "hotel_id": "string",      "prices": [        {          "date": "2019-08-24",          "average_nightly_price": {            "amount": 0,            "currency": "string"          }        }      ]    }  ],  "meta": {    "supplier": "LITEAPI"  }}

Price your selected hotels POST

You price up to 10 hotels for the same stay and room occupancies; split a longer search page across several requests. You name them by the service's hotel_ids, or by supplier with that supplier's supplier_hotel_ids from search, never both. You request at most 250 offers in total, hotel IDs times max_offers_per_hotel, to bound the response. Request hotels from one supplier at a time. Each returned offer_reference binds the complete room selection, stay, source market and price to your organization. Pass it to prebook before expires_at. You receive every room in rooms, in your requested occupancy order, with its available display and cancellation terms. Top-level room_type and board remain first-room summaries; total and any offer-level policy cover the whole stay and are counted once. You review the confirmed terms again after prebook. Promotions list each promotion once with the room positions it applies to; the total already includes them. Amounts use major currency units.

Read hotel details and reviews GET

You retrieve content using a hotel_id returned by the service. You receive cached content while stale sources refresh in the background. A supported source that has never been fetched is retrieved before the response; a failure returns a supplier error while retaining any source successfully saved. Details and reviews refresh independently. Null means a supplier has not provided the value. Images and reviews are capped at twenty each. Reviewer names are omitted.