Skip to main content
Dataset Status reports per-dataset coverage and freshness in one place. Each entry is one dataset family, saying whether it is available, whether a backfill is pending, and when it last refreshed. The endpoint is free, so it can be polled from your own monitoring.
Plan: Free and above · Credits: free (not metered)

​
What You Can Use Dataset Status For

Check whether a dataset is ready for the company set you care about before running a large job. Monitor freshness from your own systems. Distinguish a dataset that is still backfilling from one that has no data for a company.

​
Key Dataset Status Fields

coverage and coverage_pct describe how much of the universe is covered. last_sweep_at is when coverage was last measured. families lists each dataset family with available, pending, last_refreshed_at and a note. generated_at timestamps the response itself.

​
How Coverage Is Reported Elsewhere

Every cursor-based dataset response also carries its own coverage block beside data, with available_from, available_to, update_frequency and history_status. Read those from the response rather than hard-coding a date from documentation. Several datasets are backfilled backwards — newest first, reaching further into the past over time — so their start date moves.

​
Dataset Status Date Convention

last_refreshed_at on a family is when that family last ingested, not when its newest row is dated. A daily dataset that refreshed an hour ago normally has a newest row dated the previous trading day.

​
Query Dataset Status

Use the status endpoint. It costs no credits.
Two service endpoints sit alongside it: a health check and a readiness check, both unauthenticated and both intended for load balancers rather than for callers. See also Coverage and freshness for how to read a coverage block, Plans and credits for the other free discovery endpoints, and API Usage.