Documentation
Data freshness and limits
Freshness, quotas, exports, and rate limits vary by product and plan. Use this page to check what is current before you build around a specific source.
Best for
Teams that need to know how often data refreshes, what happens at the limit, and when export is available.
Freshness is source-specific
opendata does not promise one global refresh cadence across the catalog. Each product page is the source of truth for cadence and coverage.
- • Some sources update within hours
- • Some update daily or on publication
- • Some update weekly or on their own source schedule
Limits depend on the plan
Free plans are for evaluation. Export, recurring delivery, and higher quota ceilings depend on the plan you choose.
- • The API returns a clear 429 when a quota is exceeded
- • Plan pages show what is included before you upgrade
- • One key can cover recurring use without adding another credential
How to check freshness
Use the product page, source catalog, and request examples to confirm the latest available cadence before you build a workflow around a single source.
- • Check the product detail page for the latest notes
- • Use the raw catalog when you need schema or source detail
- • Compare the plan if export or recurring use matters
When you need tighter SLAs
If you need a stricter refresh window or dedicated delivery path, talk to us before you rely on the data for a production workflow.
- • Document the cadence you actually need
- • Plan for a fallback if the source is temporarily stale
- • Use the contact path on pricing or support pages to ask early
Freshness should be checked where the data lives.
Product pages and raw catalog pages are the best place to confirm cadence, fields, and the latest available coverage before you ship a workflow.