Caching Behavior - SportsAPI Pro

All V4 responses are cached in-memory upstream with endpoint-specific TTLs. Concurrent requests for the same upstream URL share a single fetch (request coalescing), so high concurrency does not cause upstream amplification.

TTL Reference

Endpoint	TTL	Notes
`/api/v1/sports`	1h	Rarely changes
`/api/v1/bookmakers`	1h
`/api/v1/bookmakers/top`	1h
`/api/v1/bookmakers/payouts`	1h
`/api/v1/navigation`	1h
`/api/v1/matches` (inplay)	30s	Fast refresh for live
`/api/v1/matches` (other)	2m
`/api/v1/matches/smart-bets`	2m
`/api/v1/odds/max` (inplay)	30s
`/api/v1/odds/max` (other)	2m
`/api/v1/polls`	5m
`/api/v1/tipsters`	10m
`/api/v1/match/{id}`	1m
`/api/v1/match/{id}/odds`	1m
`/api/v1/match/{id}/odds-movements`	2m
`/api/v1/match/{id}/markets`	5m
`/api/v1/match/{id}/prediction`	5m
`/api/v1/leagues`	10m
`/api/v1/categories`	10m
`/api/v1/league/{id}/standings`	10m
`/api/v1/league/{id}/top-scorers`	10m
`/api/v1/league/{id}/outrights`	5m
`/api/v1/league/{id}/special-offers`	1h
`/api/v1/team/{id}`	10m
`/api/v1/team/{id}/matches`	5m
`/api/v1/team/{id}/offers`	1h
`/api/v1/news`	10m
`/api/v1/world-cup`	2m / 10m	Matches 2m, standings/outrights 10m
`/api/v1/world-cup/matches`	2m
`/api/v1/world-cup/standings`	10m
`/api/v1/world-cup/outrights`	5m
`/api/v1/world-cup/predictions`	2m / 10m
`/api/v1/world-cup/special-offers`	1h
`/api/v1/world-cup/news`	10m

Stale Fallback

If the upstream is briefly unavailable, the last-known cached payload continues to be served so your UI never goes blank. Check the generatedAt field if you need to detect staleness in your application.

Last modified on June 11, 2026