Supreme Court

Overview

The Supreme Court API category provides developers with programmatic access to case records maintained by the Supreme Court of India through the eCourts Mission Mode Project. Using a Case Number Register (CNR) identifier, you can initiate lookups against live judicial databases and retrieve structured case data — enabling automated legal due diligence, KYC enrichment, and litigation risk assessment at scale.

This category follows an asynchronous request pattern: you initialize a search to receive a session token, then fetch the result once processing completes. This design keeps your integrations non-blocking and resilient even when querying high-volume government judicial systems.

Category Details

Parent Category: Ecourts
Child Categories: —
APIs in this category: Supreme Court

Key Capabilities

Main Functionality

The Supreme Court APIs expose the ability to search, initialize, and retrieve case records from the Supreme Court of India's eCourts database using a CNR (Case Number Register) identifier. The category is built around a two-step asynchronous flow — initialize a search job and then fetch the result — making it suitable for high-reliability production workflows that require non-blocking I/O and resilient handling of government database response times.

CNR-Based Case Lookup

Submit a unique CNR number to initialize a search against the Supreme Court's eCourts database. The system queues the lookup and immediately returns a session token (client_id), allowing your application to proceed without waiting for the judicial database to respond.

Asynchronous Result Retrieval

Use the client_id returned during initialization to poll the fetch endpoint and retrieve completed case details. This decoupled pattern ensures your integration remains stable regardless of upstream judicial database latency or load.

Structured Judicial Data

Receive case information in a consistent, structured JSON format — including case status, filing details, and hearing history — ready for downstream processing, storage, or display in your application without manual parsing of court portal HTML.

Common Use Cases

Banking & NBFC

Insurance

Legal & Compliance

Screen loan applicants and corporate directors for active Supreme Court litigation as part of pre-disbursement due diligence

Flag borrowers with adverse court orders or pending insolvency proceedings for elevated credit risk scoring

Automate periodic litigation checks on existing borrowers to monitor for new cases during the loan lifecycle

Enrich KYC profiles with real-time judicial data to build a more complete picture of counterparty risk

Integration Considerations

Best Practices

Handle the async flow correctly: Always persist the client_id returned by the initialize endpoint before polling the fetch endpoint. Never assume the result is ready immediately after initialization.

Implement polling with backoff: Poll the fetch endpoint at a sensible interval (e.g., every 3–5 seconds) and apply exponential backoff on retries to avoid hitting rate limits during high-traffic periods.

Use environment-specific tokens: Sandbox and production environments require separate JWT Bearer tokens. Never use a production token in development or testing workflows.

Validate CNR format before submission: Validate cnr_number format on the client side (e.g., SCIN010412962025) before calling the API to reduce unnecessary requests and improve response times.

Audit and retain client_id values: Log all client_id values with associated request metadata for traceability, debugging, and compliance audit trails.

Important Limitations

Asynchronous only: Results are never returned synchronously. All lookups require the two-step initialize-then-fetch pattern; there is no single-call endpoint that returns case data directly.

CNR dependency: Lookups require a valid, known CNR number. The API does not support name-based or party-based searches within this category.

Government database availability: Response times and availability are partially dependent on the upstream eCourts government infrastructure and may be subject to maintenance windows or degraded performance during peak periods.

Data freshness: Case data reflects the state of the eCourts database at the time of the query. There may be a lag between actual court activity and data availability on the government portal.

Rate limits apply: Excessive polling or bulk requests without backoff may result in 429 Too Many Requests responses. Design your integration to respect rate limit headers.

How APIs in this Category Work Together

The Supreme Court category is built around a two-step API pattern where each endpoint plays a distinct, complementary role in the same workflow. Neither endpoint is useful in isolation — the initialize endpoint creates the job, and the fetch endpoint delivers the result. Together, they form a complete, production-grade pipeline for Supreme Court case data retrieval.

Key Integration Patterns:

CNR Search – Initialize + CNR Search – Fetch Result: The core workflow. Submit a cnr_number to initialize, receive a client_id, then poll the fetch endpoint with that client_id until status transitions from pending to completed and full case data is returned.

CNR Search – Initialize + Persistent Job Store: Store the client_id and originating cnr_number in your database immediately after initialization. This allows background workers or webhooks to retrieve results asynchronously without relying on a live user session.

CNR Search – Fetch Result + Downstream Risk Engine: Once case data is retrieved, feed structured results directly into a risk scoring engine, compliance dashboard, or KYC enrichment pipeline for automated decisioning.

A typical end-to-end workflow looks like this: your application collects or generates a CNR number, calls the initialize endpoint to register the search job and stores the returned client_id, then a background worker polls the fetch endpoint on a schedule until the result is ready. Once status is completed, the structured case data is extracted and pushed to your risk, compliance, or case management system — all without blocking your primary user-facing flow.

The Supreme Court category sits within the broader Ecourts parent category, which covers judicial data access across multiple levels of India's court hierarchy. When building comprehensive litigation intelligence or legal KYC workflows, this category is most effective when used alongside other court-level categories that together provide nationwide coverage from district courts up to the apex court.

Related Categories include:

High Courts: Provides CNR-based case lookup for High Courts across Indian states, following the same asynchronous initialize-then-fetch pattern. Use alongside the Supreme Court category to track cases that may move between court levels.

District Courts: Enables case searches at the district and sessions court level, extending litigation coverage to lower judiciary. Essential for building a complete picture of a party's legal history across all court tiers.

KYC & Identity Verification: Identity APIs (PAN, Aadhaar, GST) are frequently combined with court search APIs to build enriched, multi-signal KYC profiles that include both identity verification and litigation risk signals in a single workflow.

Combining the Supreme Court, High Courts, and District Courts categories gives your application full-spectrum judicial coverage across India's three-tier court system. This is particularly valuable in credit underwriting, insurance fraud detection, and legal due diligence workflows where a party's litigation history at any level of the judiciary is material to the decision. Pairing these with identity verification APIs from the KYC category further strengthens the end-to-end due diligence pipeline by ensuring that the entity being searched is correctly identified before court records are queried.

Overview#

Key Capabilities#

Common Use Cases#

Integration Considerations#

How APIs in this Category Work Together#

Related Categories#

Overview

Key Capabilities

Common Use Cases

Integration Considerations

How APIs in this Category Work Together

Related Categories