Discover/Indo Court Atlas API
live

Indo Court Atlas APIindocourtatlas.com

Search and browse Indonesian court cases, legal decisions, and judicial records. Access case parties, verdicts, judges, and court metadata via 2 endpoints.

This API takes change requests — .
Endpoint health
verified 3h ago
search_cases
list_cases
2/2 passing latest checkself-healing
Endpoints
2
Updated
4h ago

What is the Indo Court Atlas API?

The Indo Court Atlas API provides access to Indonesian judicial records through 2 endpoints — search_cases and list_cases — covering case numbers, party names, verdict dates, judges, clerks, and court classifications from courts across Indonesia. Use search_cases for full-text lookup by case number or party name, or use list_cases to paginate detailed records filtered by court category, case type, and year.

This call costs1 credit / call— charged only on success
Try it
Maximum number of results to return (1-100).
Search text matched against case numbers, titles, and party names.
api.parse.bot/scraper/ddbb8954-f3b4-4fb1-9562-c61acaac3891/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/ddbb8954-f3b4-4fb1-9562-c61acaac3891/search_cases?limit=5&query=korupsi' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace indocourtatlas-com-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Walkthrough: IndoCourtAtlas SDK — bounded, re-runnable; every call capped."""
from parse_apis.indocourtatlas_com_api import IndoCourtAtlas, CourtCategory, ParseError

client = IndoCourtAtlas()

# Search for corruption-related cases by keyword (returns summary fields)
for case in client.cases.search(query="korupsi", limit=3):
    print(case.register_number, case.court, case.year)

# List cases from district courts filtered by year (returns full detail)
for case in client.cases.list(court_category=CourtCategory.PN, year=2020, limit=3):
    print(case.title, case.classification, case.legally_binding)

# Drill into a single result with error handling
try:
    item = client.cases.list(court_category=CourtCategory.MA, limit=1).first()
    if item:
        print(item.register_number, item.judges, item.notes)
except ParseError as e:
    print(f"request failed: {e}")

print("exercised: cases.search, cases.list")
All endpoints · 2 totalmissing one? ·

Full-text search across all Indonesian court cases. Matches case numbers, titles, and party names. Returns summary records ordered by relevance with a subset of case fields (id, registerNumber, title, parties, court, courtCategory, year, verdictDate). Use list_cases for full record detail.

Input
ParamTypeDescription
limitintegerMaximum number of results to return (1-100).
queryrequiredstringSearch text matched against case numbers, titles, and party names.
Response
{
  "type": "object",
  "fields": {
    "cases": "array of case summary objects with id, registerNumber, title, parties, court, courtCategory, year, verdictDate",
    "query": "the search query echoed back"
  },
  "sample": {
    "data": {
      "cases": [
        {
          "id": "847d0ebc856b9cb57cbe75d31c7591ea",
          "year": null,
          "court": "PN Mamuju",
          "title": "Putusan PN MAMUJU Nomor 232/Pid.B/2007/PN.Mu Tahun 1970",
          "parties": ". Pidana Korupsi\n.- H. MUH. TAHIR KARIM,SE",
          "verdictDate": null,
          "courtCategory": "PN",
          "registerNumber": "232/Pid.B/2007/PN.Mu"
        }
      ],
      "query": "korupsi"
    },
    "status": "success"
  }
}

About the Indo Court Atlas API

What the API Returns

The search_cases endpoint accepts a required query string and matches it against case numbers, titles, and party names across the full Indonesian court database. Results come back as summary records — each including id, registerNumber, title, parties, court, courtCategory, year, and verdictDate — ordered by relevance. The endpoint echoes the original query back in the response. You can cap results with an optional limit parameter (1–100).

Detailed Case Records via list_cases

The list_cases endpoint returns paginated, detailed case records. In addition to the summary fields available from search, these records include judges, clerk, classification, verdict notes, and related metadata. You can filter by court_category (a category code), case_type (using Indonesian court labels such as 'Pidana Umum' or 'Perdata Khusus / PHI'), and year. Pagination is controlled via page and limit parameters; the response includes total so you can calculate how many pages exist for a given filter set.

Coverage and Filtering Notes

Case type values use the labels as defined by Indonesian courts — for example, 'Pidana Umum' for general criminal cases and 'Perdata Khusus / PHI' for special civil/industrial relations cases. Omitting court_category returns cases across all categories. The year filter narrows records to a specific filing year. Both endpoints return results in Indonesian as court records are natively in Bahasa Indonesia.

Reliability & maintenanceVerified

The Indo Court Atlas API is a managed, monitored endpoint for indocourtatlas.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when indocourtatlas.com 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 indocourtatlas.com 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.

Last verified
3h ago
Latest check
2/2 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Identify prior rulings involving a specific company or individual using search_cases with party name queries
  • Build a legal research tool that filters Indonesian criminal cases (Pidana Umum) by year using list_cases
  • Track verdict dates across courts for a specific case type to analyze judicial timelines
  • Cross-reference register numbers from documents against court records to verify case existence
  • Compile judge and clerk assignment data across court categories for judicial workload analysis
  • Monitor newly filed cases in a specific court category by paginating list_cases filtered by year
  • Research industrial relations tribunal (PHI) decisions using the Perdata Khusus / PHI case type filter
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 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.

Frequently asked questions
Does indocourtatlas.com have an official developer API?+
Indo Court Atlas does not publish an official public developer API or documented REST/GraphQL interface for third-party use. This Parse API provides structured programmatic access to the data on the site.
What does `list_cases` return that `search_cases` does not?+
list_cases returns full case records that include judges, clerk, classification, and verdict notes alongside the standard summary fields. search_cases returns only the summary subset — id, registerNumber, title, parties, court, courtCategory, year, and verdictDate — ranked by relevance to the query string.
Can I retrieve the full legal text or document attachments for a case?+
Not currently. The API returns structured metadata fields — including register number, parties, verdict date, judges, and classification — but does not expose downloadable decision documents or the full text of rulings. You can fork this API on Parse and revise it to add an endpoint that fetches document content for a given case ID.
Are court categories and case types documented somewhere?+
Court category codes and case type strings use the labeling system of Indonesian courts. Known examples include 'Pidana Umum' for general criminal matters and 'Perdata Khusus / PHI' for industrial relations civil cases. Omitting court_category from list_cases returns records across all categories, which is a practical way to discover valid values from live data.
How does pagination work in `list_cases`, and is there a hard limit on results?+
The list_cases response includes page, limit, and total fields. Use the page parameter to step through results and limit (1–100) to control page size. The total field tells you how many records match the current filter combination, so you can calculate the number of pages needed to consume the full result set.
Page content last updated . Spec covers 2 endpoints from indocourtatlas.com.
Related APIs in Government PublicSee all →
ecourtsindia.com API
Search and retrieve detailed information about court cases across India's Supreme Court, High Courts, and District Courts from a database of over 239 million cases. Find case details, track legal proceedings, and access comprehensive court records to stay informed about judicial matters across the Indian court system.
judyrecords.com API
Search and retrieve detailed court records including case information and statistics from a comprehensive legal database. Access specific case details and view aggregated court record stats to research legal proceedings and case outcomes.
indiankanoon.org API
indiankanoon.org API
judgments.ecourts.gov.in API
Search for Indian court judgments and orders across multiple courts to access legal rulings, case decisions, and judicial orders. Find relevant court cases by searching through a comprehensive database of Indian judicial decisions.
bailii.org API
Search and retrieve court judgments and case law from British and Irish courts across multiple jurisdictions, with filtering by date range and location. Access complete case details including full judgment text and metadata to research legal precedents and decisions.
courtlistener.com API
Search through millions of court opinions and RECAP docket documents across 471 jurisdictions to find relevant legal cases and filings for your research. Access free legal information from CourtListener to quickly locate court rulings, case documents, and docket details without subscription fees.
oscn.net API
Search Oklahoma State Court Network records across 80+ counties to find cases, review detailed docket information, and track daily court filings. Quickly look up case details by county and district court type to stay informed on legal proceedings and filing activity.
austlii.edu.au API
Search and access Australian legal cases from AustLII's comprehensive database, browsing by year and downloading decisions in multiple formats including RTF, PDF, and print-friendly versions. Discover available case databases and retrieve specific court rulings with prioritized download options to suit your preferred format.