Concepts
Caching
Cache responses to cut latency and stay within rate limits.
Cache search responses in a KV store for up to 60 minutes. Prices and availability change, so 60 minutes is the ceiling — but caching even for a few minutes guards against rate limits and burst traffic.
The X-Cache header
Every response carries X-Cache: HIT or X-Cache: MISS, so you can see whether a result came from the Direct Travel API's own cache.
Caching is for live, short-lived consumption. You may not hard- or cold-store listings in your own database, and you may not use the API for data analysis. See the Overview for usage restrictions.
What to read next
- Pricing & quotes — why prices are short-lived
- Rate Limits — what caching helps you stay within
- Pagination — caching paged requests