Overview
Jurisdictions represent the US states and territories supported by CaseXchange. Each jurisdiction has a two-lettercode and a display name. Counties are a related resource — every county belongs to exactly one jurisdiction and can be fetched independently or filtered by jurisdiction code.
Both endpoints require the read_only API key tier and authenticate via the X-API-Key header.
Endpoints
List jurisdictions
Returns an array of{ code, name } objects for every supported US state and territory.
code value when filtering counties or setting the jurisdiction on a case.
List counties
Returns counties, optionally filtered by one or more jurisdiction codes via thejurisdictionCodes query parameter.
Query parameters
jurisdictionCodes the response includes every county across all jurisdictions. Filter to keep payloads small when you only need specific states.
Use cases
- Power jurisdiction and county dropdowns when creating or filtering cases.
- Validate inputs client-side before calling
POST /sent-cases. - Combine with firm specialties to narrow destination firms by region.
- Use the counties endpoint to build a two-step picker: select a jurisdiction first, then load its counties.
Jurisdiction codes follow standard postal abbreviations. Use uppercase strings in requests.
Related
- Reference Data examples — full curl examples for jurisdictions, counties, and case types.