Docs
/
Getting started
/
Caching & TTL

Caching & TTL

Responses are cached so repeated calls are fast. An endpoint's TTL says how old a response can be.

Cache TTL

TTLs across the catalog run from 5 sec to 24 hr. Each endpoint lists its own TTL under its Endpoints tab; for example /agoda/destinations/country-cities has a TTL of 1 hr. Only GET responses are cached.

Cached calls are still paid

Caching changes how fresh the data is, not what a call costs. Every call is paid at the endpoint price, whether the response comes from the cache or from the actor.