Endpoints
Search Extracted Rules
Query validated extracted filing rules from active source documents, including state court e-filing, timing, service, fee, courtesy-copy, and courtroom rules
GET
Search and page through every rule we hold, across all courts. Filter by court, judge, rule type, workflow phase, case type, or text. Results are newest first and paged with
Rules are ordered newest first. If the court’s documents are re-checked while you page, a rule can move between pages; re-read from
limit and offset.
string
Court identifier, such as
il-cook-circuit, ca-los-angeles-superior, or edny.string
Judge, calendar, department, or courtroom slug. Court-level rules use
court.boolean
When
judge_slug is supplied, include court-level rules where judge_slug is court. Defaults
to true.string
Filter by structured rule type, such as
ElectronicFilingRule, FilingTimingRule, ServiceRule,
FilingFeeRule, or CourtesyCopyRule.string
Filter by workflow phase, such as
FILING, CASE_INITIATION, or MOTION_PRACTICE.string
Filter by case type. General rules and rules without an explicit case-type limit are included.
string
Search summary, source text, tags, and structured data. Every word must appear in the rule.
Example:
rejected cure.number
Maximum rules per page. Defaults to
100, maximum 500.number
Number of matching rules to skip. Defaults to
0. Pass meta.next_offset from the previous page
to read the next one.Response fields
array
Validated extracted filing rules with provenance.
object
The validated extracted rule payload. It includes source text, summary, tags, workflow phase,
severity, structured data, and citation details when captured.
string
Official source URL for the rule.
string
Source document version used for the extraction.
object
Paging
Read a whole court by followingnext_offset until it is null:
offset=0 when you need an exact snapshot.
Filtering behavior
Whenjudge_slug is provided, the endpoint returns rules for that unit. With include_court_rules=true, the response also includes court-level rules for the same court. This lets clients combine court rules with judge, calendar, department, or courtroom overrides.
This endpoint exposes raw extracted rules first. It does not yet resolve conflicts or compute the final effective rule set for a filing.
Limits
- Text and case-type searches:
qandcase_typeread every candidate rule before matching, up to 10,000 candidates. That covers any single court. A search across all courts with a common word returns422; adddistrict_id,judge_slug,logic_type,workflow_phase, or more specific words. - Unknown court: a
district_idwe do not map returns404.
/rules.