Skip to main content
corpusType chooses which body of law a search runs against. It is the single most important filter in the API: it decides whether you get a statute, a regulation, a court rule, agency guidance or a decided case.
Pass one token or a list. This page is the query vocabulary: what each token means and how to scope it. For how much data sits behind each one and what is deliberately excluded, see API Coverage.

Scoping rules

1

A federal token needs only corpusType

2

A state token needs corpusType and state

Omit state on a state-scoped token and the search spans every jurisdiction that has that corpus ingested, which is rarely what you want and always costs the same.
state also accepts a list, so one call can cover several jurisdictions.
3

Narrow further with source, where a token folds in several bodies

titleNumber is only valid alongside corpusType USC or CFR. Sending it with any other token returns a 422.

The 19 tokens

Sizes are distinct sections, measured 2026-09-07. Call GET /us/statutes/coverage for a live figure and for which tokens have data in which jurisdiction.

Federal-scoped

State-scoped

Each of these requires state, or spans every jurisdiction holding that corpus.

Choosing between tokens that look alike

Five pairs are routinely confused, and picking the wrong one returns a confident answer to a different question. For asking any corpus what it said on a past date, see Point-in-time law. SESSION_LAW and STATUTE_COMPILATION both carry goodLawStatus: "unknown" by design: they are historical records, not statements of current law.

Filtering to one named source

AGENCY_GUIDANCE, AGENCY_ADJUDICATION, FEDERAL_RULES, CFR, US_TAX_TREATY and STATE_AGENCY_GUIDANCE each fold several independently filterable bodies into one token. Every result carries a source field naming which one it came from; pass that value back as the source filter to scope to it.
source accepts a single value or a list, so source: ["frcp", "sct"] searches both in one call. An unrecognized value is rejected with 422 and the error names every valid code, so the API itself is the authoritative list.
The far and dfars sources split existing Title 48 data by chapter. They are not a separate ingest and do not add sections to the CFR total.

API Coverage

How much sits behind each token, and what each corpus deliberately excludes.

Jurisdictions and state codes

The 52 jurisdictions and how to discover live coverage.
Last modified on September 7, 2026