OSCN APIoscn.net ↗
Access Oklahoma State Court Network records via API: district court cases, dockets, daily filings, statutes, and appellate opinions across 80+ counties.
What is the OSCN API?
This API provides 10 endpoints covering Oklahoma State Court Network (OSCN) records across 80+ counties. Use search_cases to find district court cases by party name, case type, or date range; get_case_details to pull full docket entries and party lists; or get_statute to retrieve statute text, legislative history, and Citationizer citation data for any section of the Oklahoma Statutes.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/36371741-d78c-4d8e-8eac-70ab6b987f9f/list_counties' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns all Oklahoma county/court database identifiers available for search. Each entry includes a lowercase id (e.g., 'tulsa', 'oklahoma') and the full court name. Use the id value as the db parameter in other endpoints.
No input parameters required.
{
"type": "object",
"fields": {
"items": "array of county objects with id and name"
},
"sample": {
"data": {
"items": [
{
"id": "tulsa",
"name": "Tulsa County District Court"
},
{
"id": "oklahoma",
"name": "Oklahoma County District Court"
}
]
},
"status": "success"
}
}About the OSCN API
District Court Case Data
The search_cases endpoint accepts filters including db (county identifier from list_counties), lname/fname for party name, case_type (from list_district_court_case_types), and a filing date range via filed_date_l and filed_date_h. Results return up to 500 case summaries per query — each with case_number, date_filed, style, found_party, and a cmid used to precisely target get_case_details. The case detail response includes a header object (Style, Judge, Filed date), a parties array with name and role, and docket_entries with date, code, description, and attached documents.
Daily Filings and Foreclosure Search
get_daily_filings_by_county returns all cases filed on a given past date for one of approximately 13 supported counties (including Tulsa and Oklahoma). The date parameter must be a completed past day; the current date returns empty results. search_foreclosure_cases narrows civil filings further: it scans CJ (Civil relief over $10,000) cases for a county and date range, inspects each for mortgage foreclosure indicators, and returns structured results with plaintiff, defendants, has_more, and next_offset for pagination. The limit parameter is clamped at 40 candidates per call.
Oklahoma Statutes
list_statute_titles returns all statute title codes and a scope string showing the current legislative session. list_statute_sections expands any title into its full section list with cite_id, section, name, and heading. get_statute returns the full text, history note, and Citationizer data — citing_documents (opinions and AG opinions that cite the section) and table_of_authorities (documents the section cites) — each entry carrying a cite_id that feeds directly into get_case_opinion.
Appellate Opinions
get_case_opinion retrieves a published OSCN appellate opinion by citation string (e.g. 1998 OK CR 6) or cite_id. The response includes full text (which can exceed 100,000 characters for longer opinions), citations (parallel cite array), decided date, court, and inline_references identifying cited documents within the opinion body. Opinions can be discovered via the Citationizer data returned by get_statute.
The OSCN API is a managed, monitored endpoint for oscn.net — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when oscn.net changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official oscn.net API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Monitor new district court filings in a county by polling get_daily_filings_by_county each morning
- Build a party-name alert system using search_cases with lname/fname filters across multiple db counties
- Track mortgage foreclosure activity in a county and date range with search_foreclosure_cases and its next_offset pagination
- Retrieve full docket history and party roles for a specific case number using get_case_details with cmid for precision
- Look up the current text of any Oklahoma statute section and its legislative history via get_statute with cite_id
- Find all appellate opinions that cite a specific statute section using Citationizer citing_documents from get_statute
- Cross-reference an appellate opinion's table of authorities by resolving each cite_id through get_case_opinion
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.