Per-state rate-data refresh status
GET /v1/freshness
Per-state status of TaxQL’s rate-data refresh pipeline — for each US state: last_fetch (freshest source file pulled), status (the refresh outcome), source_period (YYYYQN of the freshest effective row), the state class, and loaded row count. Public endpoint (no API key).
Two distinct time signals (read both together). last_refreshed_at is when the pipeline last successfully refreshed this state (an ISO timestamp — the scheduled run). effective_through is how old the held data is — the newest effective date the rate data reflects (an ISO date). They answer different questions and must not be conflated: a recent last_refreshed_at with an old effective_through means we refreshed on schedule and the source simply has not published a newer rate (e.g. a state whose local rates have not moved in years). source_period is the same effective signal as a YYYYQN label; it is populated for every state including CA/FL/TX/WA (which read null before 2026-08-14).
What status means — and does NOT mean. It reports the refresh PIPELINE: whether the scheduled load ran and how recent the loaded data is — NOT whether our rate matches the publisher’s newest published edition. Values: ok (loaded, current for its class), changed (data moved on the last load), stale (loaded data is aging past its class threshold), failed (last refresh errored; last-good data still served), static (migration-seeded, no feed), plus maintenance / manual / unknown / anchor_regression. Edition-level currency (does our data match the publisher’s latest release) is monitored internally and is unevaluable for some states (e.g. FL, LA, VA — the publisher exposes no cheap edition marker); it is NOT surfaced here. Canada provinces are not included. See https://docs.taxql.com/concepts/freshness for the field guide.
Responses
Section titled “ Responses ”Per-state freshness snapshot.