Skip to main content
GET
Use this endpoint when you need filing-rule intelligence directly from the extraction store. It does not use the older federal /rules profile shape.
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. Example: rejected cure.
number
Maximum rules to return. Defaults to 100, maximum 500.

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.

Filtering behavior

When judge_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.