Dataset scope, freshness and the Candid compatibility matrix
What is in the corpus, how current it is, and which Candid parameters this API honors. This is the answer to Candid's last_updated filter: there is no per-row change stamp because the dataset is rebuilt as a whole from monthly IRS releases, so a client keeping its own copy in sync watches dataset.version and the fiscal year span here and re-pulls when either moves. Keyless and unmetered.
scope carries TWO fiscal-year ends and they are not the same number. last_fiscal_year is the newest year any row falls in — sync against this. last_complete_fiscal_year is the newest year that has finished arriving, and it is the one to quote in prose: the IRS releases e-file data 12-24 months after the activity, so the corpus always holds a few hundred early filings for a year that has barely begun. partial_fiscal_years names every year still filling. Reporting last_fiscal_year as the coverage span overstates it by a year or two.
Request
- Base URL: https://data.useplinth.com
- URL: https://data.useplinth.com/api/v1/meta
- Auth: none required
Query parameters
Filing jurisdiction of the GRANT: us (default) | ca. Never mixed — amounts stay in the currency the filing was made in and are never converted, so every total is a single-jurisdiction total. x_plinth.dataset names the source, licence and currency behind the answer. Distinct from country, which is where the RECIPIENT sits.
Response
What this deployment holds, and how to get a key.
Changes
No recorded changes to this operation across all 1 revision of this API.