actId.
It is stable, unique, and the key you use to fetch a section’s metadata and full
text. You never construct an actId by hand. You get it from search results and
pass it back to the section endpoints.
What an actId looks like
actId values encode the section’s place in the source hierarchy. A few examples:
State sections follow the same idea, encoding the state’s code and section
structure. Treat the whole string as an opaque key: read it from a result, store
it, and pass it back unchanged.
The workflow
1
Search to get an actId
POST /statutes/search returns result objects, each with an actId.2
Fetch section metadata
GET /statutes/section/{actId} returns the full result object for that one
section (citation, hierarchy, source URLs).3
Fetch full text
GET /statutes/section/{actId}/body returns the section’s full text.
Returned only when text is available.Result and hierarchy fields
Search results and thesection object share the same shape. Alongside actId,
these fields describe where a section sits and how to cite it:
titleNumber can be alphanumeric (some states use ids like 13A), so treat it
as a string, not an integer.Example: search, then fetch
This walks the full path: run a search, take the firstactId, fetch its
metadata, then fetch its body.
Related
Response Formats
The text formats and source URLs a section can carry.
Corpus Types
The corpusType tokens you filter a search by.

