Get weather for your hotel stay
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.
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
^bkg_[a-zA-Z0-9-]+$length <= 128Header Parameters
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
application/json
curl -X GET "https://example.com/v1/hotel/bookings/string/weather"{ "data": { "booking_id": "string", "hotel_id": "string", "start_date": "2019-08-24", "end_date": "2019-08-24", "units": "metric", "days": [ { "date": "2019-08-24", "temperature_min": 0, "temperature_max": 0, "summary": "string", "conditions": [ { "description": "string", "icon": "string" } ], "humidity_percent": 0, "afternoon_humidity_percent": 0, "wind_speed_mps": 0, "maximum_wind_speed_mps": 0, "precipitation_probability": 0, "precipitation_total_mm": 0 } ] }}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.
Cancel your hotel booking POST
You request cancellation of all remaining rooms. Cancellation continues asynchronously; read your booking for its current state and attempt history. Repeated requests reuse an active attempt, and can resume its failed workflow. A canceled stay remains canceled while refunds are processed. Your cancellation refund is the recorded intent, not confirmation of settlement; a null refund requires review. Its refund_to names the payments the refund returns to once the attempt completes.