One enforcement matter, with its chain
The matter plus its EVENTS (timeline), PARTIES, RELIEF, statutory CITATIONS and the SOURCE DOCUMENTS each claim traces to. This is the dossier the product is sold on.
THE CHAIN IS WHAT IS METERED. Below the paid step each chain is a 2-row sample and data.chain_totals reports the true size of every one of them — never an empty wall, and never a sample you cannot tell is a sample. Listing and searching matters stays fully open.
FIELDS THAT LOOK LIKE HEDGES AND ARE THE PRODUCT: events[].is_date_estimated (the source gave a year, not a day), verification, laws[].link_status (unlinked = we hold the citation verbatim but have not resolved it — a confidently wrong citation is worse), and duplicate_of.
PARTIES ARE REDACTED BY POLICY, in the database, not here: 97 of 235 party rows publish and the rest are withheld — named private individuals and minors by default. See the pii_class and redaction_policy vocabularies on /enforcement/categories.
A 404 is returned both for a matter that does not exist AND for one withheld pending review, on purpose: distinguishable codes would turn the readiness gate into an enumeration oracle.
Request
- Base URL: https://ai-law-tracker.com/api/v1
- URL: https://ai-law-tracker.com/api/v1/enforcement/matters/{matter_uid}
- Auth: one of:
- API key in header X-API-Key
- HTTP bearer
Path parameters
An opaque stable key, not a description — read caption for the matter name.
Response
The matter, with parties, events, relief, cited statutes and source documents.
Changes
No recorded changes to this operation across all 1 revision of this API.