Docs
Get an API key
Hotel content

Read hotel details and reviews

GET
/v1/hotel/content/{hotel_id}

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.

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

Path Parameters

hotel_id*string
Match^htl_[a-zA-Z0-9-]+$
Lengthlength <= 128

Header Parameters

x-request-id?string

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

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/v1/hotel/content/string"
{  "data": {    "hotel_id": "string",    "name": "string",    "description": "string",    "chain": "string",    "star_rating": 0,    "guest_rating": 0,    "review_count": 0,    "address": "string",    "city": "string",    "country": "string",    "zip": "string",    "latitude": 0,    "longitude": 0,    "main_photo": "string",    "thumbnail": "string",    "phone": "string",    "email": "string",    "time_zone": "string",    "check_in_start": "string",    "check_in_end": "string",    "check_out": "string",    "important_information": "string",    "pets_allowed": true,    "child_allowed": true,    "parking": "string",    "amenities": [      "string"    ],    "images": [      {        "url": "string",        "hd_url": "string",        "caption": "string",        "order": 0,        "is_default": true      }    ],    "rooms": [      {        "name": "string",        "photos": [          {            "url": "string",            "hd_url": "string",            "caption": "string",            "order": 0,            "is_default": true          }        ]      }    ],    "policies": [      {        "type": "string",        "name": "string",        "description": "string"      }    ],    "points_of_interest": [      {        "name": "string",        "category": "string",        "distance_km": 0,        "importance": "string"      }    ],    "sentiment": {      "categories": [        {          "name": "string",          "rating": 0,          "description": "string"        }      ],      "pros": [        "string"      ],      "cons": [        "string"      ]    },    "reviews": [      {        "score": 0,        "headline": "string",        "pros": "string",        "cons": "string",        "date": "string",        "language": "string",        "traveler_type": "string",        "country": "string",        "source": "string"      }    ]  }}

See a daily price index for your hotels POST

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.

Get weather for your hotel stay GET

You receive daily weather for your stored hotel coordinates and stay dates, including checkout day, regardless of your booking supplier. You need the same organization and user headers as a booking read. Measurements use metric units. Forecasts beyond one week are less reliable. You receive only available days; missing days and optional fields are unknown. Repeating this read requests fresh weather without changing your booking.