Search and track new federal court cases by practice area using the UniCourt Enterprise API with OAuth2 authentication
domain: unicourt.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Exchange your UniCourt CLIENT_ID and CLIENT_SECRET for an access token via the documented OAuth2 client credentials endpoint in the UniCourt Enterprise API
Include the access token as a Bearer token in the Authorization header of all subsequent requests
POST to the case search endpoint with a JSON payload specifying the practice area, court ID, date range, and any party or attorney filters
The response returns a list of case summaries; fetch individual case detail including parties, attorneys, docket entries, and documents using the case-specific endpoint and the caseId from the search results
Register a case tracker by calling the case-tracking endpoint with the caseId to receive updates when new docket entries are filed
Known gotchas
UniCourt's API is an enterprise product with tiered pricing; ensure your subscription tier includes the specific court jurisdictions and data types your workflow requires
OAuth2 access tokens expire; implement token refresh logic using the client credentials flow rather than storing long-lived tokens
UniCourt normalizes party and attorney data across courts, but the underlying court records may contain misspellings or inconsistencies that affect entity matching accuracy
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?