Overview

How the Direct Travel API resolves locations, prices stays, paginates, clusters, and shapes its responses.

These pages explain how the Direct Travel API behaves so the endpoint reference can stay short.

Locations & geocoding — the four ways to say where to search
Response & supplier model — what a result looks like and where the suppliers live
Pricing & quotes — when prices appear and what they mean
Pagination — paging through results and reading meta.total
Clustering — summarizing dense map viewports into H3 markers
Caching — caching responses and reading X-Cache

Rate Limits

Request limits and best practices for the Direct Travel API.

Locations & geocoding

The four ways to tell the Direct Travel API where to search — address, coordinates, bounding box, or hotel IDs.