Court Data API

Search State and Federal Court Data Without the Busywork

Raw court data is siloed, fragmented, and hard to use reliably. UniCourt's API standardizes data (1,100+ fields across 200+ endpoints) and connects it to a knowledge graph, mapping the connections between key players, so clean data flows right into your workflows.

2B+

dockets and documents

5,000+

state and federal courts

states (more coming)

The Friction of Tracking Court Data Manually

Manual Status Checks

Without automated tracking, finding out whether a case or document order has been updated means calling the API, or the court, again and again. UniCourt’s webhooks push real-time alerts the moment something changes.

Fragmented By Court

Searching state and federal court data usually means working across separate portals with different rules. UniCourt’s API covers both in one place with the same jurisdiction, case type, and status filters you’d use in the app.

Manual Account Admin

Checking your billing cycle, downloading invoices, or reviewing what your team is tracking traditionally requires logging into your account first. UniCourt delivers all of it, billing usage, invoices, tracked cases, and saved searches, directly via API.

UniCourt vs. Manual Court Research

Everything you need. None of what slows you down.

Feature	UniCourt’s Court Data API	Manual Court Research
Finding what you need	Powerful search capabilities across all courts	Search court by court with limited criteria
New case coverage	All new cases structured and normalized daily across state and federal courts	New cases pulled and processed one at a time
Bulk access	Access to a growing library of 400M+ court cases	Pull and process each case’s documents individually
New filings	Automated alerts on new docket updates	Manual rechecks required
Account management	Billing, invoices, and saved searches delivered via API	Log in to check billing, download invoices, review saved searches
Coverage	Federal and state courts under one integration	Separate systems per jurisdiction
Data structure	Best-in-class entity normalization	Raw party names that vary by court

Speak with an API Expert

Trusted by Legal Tech Teams

How it works

From Manual Research to Production‑Ready Data in Three Steps

A real path to production: scope it, test it, ship it.

1: Scope it with an API expert

Book a call with an API Expert to walk through your use case, data volume, integration plan, and pricing.

2: Test in your own live account

Get a trial key and run real queries against state and federal court data. Validate the schema, coverage, and workflow before you commit.

3: Go to production

Switch to production scale and start pulling normalized, deduplicated data at scale.

Built for Developers

Clean REST endpoints. Predictable JSON responses.

Consistent JSON schema across all courts, only one integration to build for all state and federal courts
WebSockets alerts for docket updates
Comprehensive API documentation with code samples
Python SDK

Speak to an API Expert

import unicourt

auth_obj, http_status_code = Authentication.generate_new_token()

caseresults, responses = CaseSearch.search_cases(q=query, page_number=1)

pacer_options = CaseUpdatePacerOptions(
    pacer_user_id="your_Pacer_username",
    pacer_client_code="Test_UniCourt_API",
)

caseupdate, response = CaseUpdate.update_case(
    case_update_request=request
)

Common questions

What Teams Ask Before Automating Court Research

How does this help me avoid manual work?

UniCourt structures and normalizes thousands of new state and federal cases daily and allows you to pull data directly into your systems, so your team isn’t manually checking court portals.

How is this different from just searching court websites directly?

State and federal court websites give you raw dockets one court at a time with limited search capabilities. UniCourt gives you one API, structured and normalized data across every covered court, plus real-time alerts.

Is there a self-service way to try this?

Access is set up as a plan built around your volume and use case, so the fastest path is a short call with an API expert.