judyrecords.com APIjudyrecords.com ↗
Search and retrieve US court case records from JudyRecords via 3 endpoints. Get case filings, hearings, attorneys, documents, fees, and database stats.
curl -X GET 'https://api.parse.bot/scraper/c3e2c409-c658-4fb8-9a0c-cae7d81d3231/search_cases?page=1&query=smith' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for court cases by keyword. Supports pagination.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination |
| queryrequired | string | Search query (e.g. name, state, case number) |
{
"type": "object",
"fields": {
"query": "string",
"results": "array of objects (case_id, title, url, snippets)",
"total_info": "string",
"current_page": "integer",
"available_pages": "array of integers"
},
"sample": {
"data": {
"query": "smith",
"results": [
{
"url": "https://www.judyrecords.com/record/dxv6wvt482d4",
"title": "Gwinnett County, Georgia Court Record",
"case_id": "dxv6wvt482d4",
"snippets": [
"1989 case type index only case status disposed party plaintiff hakman, sarah smith",
"aliases aka keller, virginia ann aka smith , h carson, iii aka taylor, sarah",
"smith hakman aka smith , r powell aka hakman, sarah smith , ii aka lewis, margaret"
]
},
{
"url": "https://www.judyrecords.com/record/daisgqn2a396c",
"title": "Tennessee Court Record",
"case_id": "daisgqn2a396c",
"snippets": [
"kristine smith vs steven craig smith 60ch1-2012-cv-5 steven craig smith",
"civil contempt steven craig smith kristine smith 08/20/2015 counter complaint",
"cross filing steven craig smith kristine smith 01/19/2012 modification of"
]
},
{
"url": "https://www.judyrecords.com/record/muj65y8j3d5c",
"title": "Tennessee Court Record",
"case_id": "muj65y8j3d5c",
"snippets": [
"tom smith & mary jo smith vs larry fisher (et. al) 60gs1-2010-cv-2716 tom smith",
"& mary jo smith , plaintiff filing date: oct 29 2010 balance due: case judge",
"date void date civil summons - 1 defendant tom smith & mary jo smith larry fisher"
]
}
],
"total_info": "Page 1 of\n\n 20,068,403 total cases for:smith",
"current_page": 1,
"available_pages": [
1,
2,
3
]
},
"status": "success"
}
}About the judyrecords.com API
The JudyRecords API exposes 3 endpoints covering US court case data indexed by JudyRecords.com. Use search_cases to query by name, case number, or keyword with paginated results, get_case to pull structured details on a specific case — including filings, hearings, attorneys, documents, and fee records — and get_stats to retrieve the current total count of indexed cases across the database.
Search and Pagination
The search_cases endpoint accepts a query string (name, state, case number, or other keyword) and an optional page integer for pagination. Results include a list of matching cases, each with a case_id, title, url, and snippets for context. The response also surfaces total_info (a human-readable summary of result count), current_page, and available_pages so you can iterate through deeper result sets programmatically.
Case Detail Fields
The get_case endpoint takes a single alphanumeric case_id and returns a structured object with up to eight data sections. general_info carries core identifiers: title, case_number, primary_party, filing_date, and status. Beyond that, the response includes filings (type, parties, filing and void dates), hearings (date, time, judge, result), attorneys (name, law firm, primary flag), documents (type, status, served-on date), fees (assessed amount, receipts, amount due), and additional_parties with roles. A context string identifies the court or jurisdiction. Note that data completeness varies by the originating court system — some cases will return partial fields.
Database Statistics
The get_stats endpoint requires no inputs and returns a total_cases_tagline string reflecting the current count of indexed cases, plus a source URL pointing to JudyRecords' info page. This is useful for monitoring index growth or displaying coverage context in an application.
- Lookup litigation history for a person or business by name using
search_cases - Pull structured hearing schedules and judge assignments for a known case via
get_case - Retrieve attorney and law firm associations across multiple case records
- Audit fee assessments and outstanding amounts due in civil cases
- Track filing dates and case statuses for a portfolio of legal matters
- Display total indexed case count in a legal research dashboard using
get_stats - Cross-reference case participants using
additional_partiesandattorneysfields
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does JudyRecords have an official developer API?+
What does `get_case` return and how complete is the data?+
general_info, filings, hearings, attorneys, documents, fees, additional_parties, and a context string for the jurisdiction. Completeness depends on the originating court — some courts expose full dockets while others provide only basic case metadata. The response will reflect whatever the source court system makes available.Can I filter `search_cases` results by state, case type, or date range?+
query and a page integer — there are no dedicated filter parameters for state, case type, or date range. You can include state names or other qualifiers in the query string to narrow results. You can fork this API on Parse and revise it to add structured filter parameters if your use case requires them.Does the API expose full document text or PDF links for case documents?+
documents array in get_case returns metadata fields — document_type, number, status, status_date, and served_on — but not full document text or direct file download URLs. You can fork this API on Parse and revise it to add a document-retrieval endpoint if your workflow requires actual document content.How is pagination handled in search results?+
search_cases returns a current_page integer and an available_pages array listing all navigable page numbers for the query. Pass the desired page number as the page input to retrieve subsequent result sets. Each page returns the same results array structure with case_id, title, url, and snippets.