federal
jurisdiction, separate from the states.
How jurisdictions are keyed
- State codes are 2-letter lowercase strings:
ca,tx,ny,fl, and so on. You pass one as thestatefilter onPOST /statutes/searchto scope a state corpus. federalis the jurisdiction for all federal corpora (USC,CFR,CONSTITUTION,FEDERAL_RULES,EXECUTIVE_ACTION,FEDERAL_REGISTER,AGENCY_GUIDANCE). Federal searches need only acorpusType, nostate.- Each jurisdiction row carries a
kindfield:federal,state, orterritory. DC and Puerto Rico areterritory.
Discovering coverage
Three authenticated discovery endpoints tell you exactly what is available.GET /statutes/coverage
The self-describing matrix. Every jurisdiction with its per-corpusType
corpora counts, plus a corpusTypes legend. Start here.GET /statutes/states
Headline counts per jurisdiction (
sectionCount, hasData, corpora).GET /statutes/codes?state=xx
The statutory codes (Penal, Civil, and so on) ingested for one state.
Live, not hardcoded
Coverage expands weekly. Read it at request time rather than baking counts
into your app.
Reading a jurisdiction’s corpora
GET /statutes/coverage returns a wrapped { "data": ..., "meta": ... }
response. Each jurisdiction in data.jurisdictions has a corpora object whose
keys are the corpusType tokens that actually have data. Read those keys to know
which searches you can scope.
Listing a state’s codes
Once you know a state hasSTATE data, GET /statutes/codes?state=xx breaks it
into its named codes so you can see how that state is structured.
Related
Corpus Types
The 11 corpusType tokens and how to pair them with a state.
API Coverage
The full jurisdiction matrix with current section counts.

