Read a saved destination
You retrieve the resolution using the service's plc_ ID from your place search. This read makes no supplier request.
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
^plc_[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/places/string"{ "data": { "id": "string", "name": "string", "address": "string", "location": { "latitude": 0, "longitude": 0 }, "suggested_radius": 1000, "country_code": "string", "city": "string", "types": [ "string" ], "alternatives": [ { "name": "string", "address": "string" } ] }}Resolve your destination GET
You receive the best matching place, its coordinates and a suggested search radius in metres. Read the address and alternatives to distinguish similarly named places. Repeat the same query, type filters and language to reuse its saved resolution. A missing id means the result could not be saved; you can still use its coordinates. The radius is bounded to 1–50 kilometres and can under-cover large regions.
Find hotels for your stay POST
You receive available hotels and their cheapest current prices for your complete party. Supply one occupancy per room with each child's age. Search one city and country, or a point with a radius in metres. Check-out follows check-in by at most 99 nights. Use the returned hotel_id, or supplier_hotel_id with meta.supplier, with offers to get a bookable price; search prices are for comparison. To read the next page, send meta.pagination.next_cursor as cursor with the same search fields; stop when it is omitted rather than at a short or empty page, and expect no estimated total.