US State Court Data: Coverage, Portals, and Limitations
State court data is more fragmented than federal court data. There is no PACER equivalent for state courts — no centralized access layer, no standard data format, and no uniform access policy. Each state operates its own case management infrastructure, and within a state, each court may present data differently. Understanding this landscape explains both what DocketLayer covers and why some limitations exist.
How State Court Data Works
Every US state has its own court system, typically organized into trial courts of general jurisdiction (Superior Court, Circuit Court, District Court depending on the state), intermediate appellate courts, and a supreme court. Some states also have specialized courts — probate, family, drug court — that operate on separate case management systems.
There is no federal mandate that states make court records electronically accessible. States that do provide public electronic access have built their own portals, on their own timelines, with their own data structures. Some states have centralized statewide portals; others delegate to individual counties; a few operate through third-party vendors like Tyler Technologies. The result is a patchwork of systems with no common standard.
Portal Types and Access Methods
State court portals fall into several broad categories, each requiring a different integration approach:
- Statewide unified portals — A single portal covers all courts in the state (e.g., Oklahoma's OSCN). These are the most straightforward to integrate: one authentication scheme, one data format, comprehensive coverage within the state.
- Tyler Technologies cloud portals — Tyler's Odyssey platform powers court systems in many states and counties. Access is through the public-facing Tyler portal, which varies slightly by jurisdiction configuration.
- Legacy county-level portals — Older states or states without statewide systems have individual county portals, each built independently. Coverage requires building separate integrations per county.
- Authenticated session portals — Some states require account creation or session-based authentication to access public records, imposing rate limits and access controls that make bulk integration more complex. West Virginia's WVPASS is an example.
Why Coverage Varies
Full coverage means real-time docket access across all case types and filing categories the portal exposes. Partial coverage means access is live but limited — either to certain case types, certain courts within a state, or data that the portal surfaces publicly but incompletely.
Coverage is partial rather than full in several situations: where a portal exposes some case types but not others; where a state has a centralized portal for superior courts but county-level portals for lower courts that have not been integrated; or where a portal's structure makes reliable extraction of certain data categories technically difficult.
Some courts are in a planned state — the integration is built, but queries are gated. Texas is the primary example: 37 courts are indexed and integrated but are not open for queries pending a commercial data agreement with the Texas Office of Court Administration.
What Is Excluded and Why
Several categories of state court are excluded from DocketLayer coverage entirely, regardless of state:
- Courts of limited jurisdiction — Traffic, small claims, municipal, and justice of the peace courts. These handle high volumes of low-stakes matters and generally do not have public electronic docket systems suitable for programmatic access.
- Juvenile courts — Juvenile proceedings are sealed or restricted in most jurisdictions as a matter of law.
- Sealed family and domestic relations proceedings — Divorce, custody, and related matters are frequently restricted from public access.
- Tribal courts — Tribal court systems are sovereign and operate under different access frameworks than state or federal courts.
Checking Coverage Before You Build
Before writing code that depends on a specific court, verify its coverage status. Call GET /v2/status and look for the court in the response. Courts with coverage: "full" or coverage: "partial" appear in the courts array and accept queries. Courts with coverage: "planned" appear in planned_coverage and return a 422 error if queried. Courts not present in the response are not currently covered.
For a browsable view of all 1,920 state courts by state, see the Court Directory.