Data freshness
Every answer carries the date we read the data behind it. Show that date to your users, and store it with any answer you keep.
Dates in every response
| FIELD | WHAT DATE IT IS |
|---|---|
evidence[].source.as_of | The date we read the directory that lists this provider for this plan year. |
data.as_of | For a check: the date of the directory that gave the answer. |
data_as_of | The newest date among the data behind the whole response. |
sources[].as_of | The date each source type is current to. |
Dates are YYYY-MM-DD. Different insurers publish on different schedules, so two answers in one batch can carry different dates. That is expected: each date is the truth for its own listing.
Check the dates without a key
GET /v1/status returns each source type with its date. It needs no key and does not count against your quota.
curl https://api.inplan.io/v1/status200 OK · application/json
{ "data": { "status": "ok", "api_enabled": true, "version": "d470109", "time": "2026-10-30T09:28:11.713Z", "checks": { "database": { "ok": true, "latency_ms": 0 }, "cache": { "ok": true } }, "datasets": [ { "type": "insurer_directory", "description": "Provider network directories published by health insurers", "as_of": "2026-10-29" }, { "type": "plan_directory", "description": "Provider network directories published by Medicare Advantage plans", "as_of": "2026-10-29" }, { "type": "provider_registry", "description": "National provider registry and practice records", "as_of": "2026-10-29" }, { "type": "plan_catalog", "description": "Published health plan catalogs", "as_of": "2026-10-28" } ] }}
Directories change
We read insurer and plan directories on a regular cycle. Networks can change between reads. Tell users to confirm with the plan or the provider before care. Every check includes a note that says so.
If you cache answers, keep as_of with them and refresh them on your own schedule.
Docs / Concepts / Data freshnessNext: Batch checks