,

Next Hearing Date API: Check 100 Indian Court Cases Against Cause Lists in One Call

The eCourtsIndia CNR batch check tells you which of up to 100 cases are on upcoming district court cause lists, with date, courtroom, item number and purpose. Live example, what each answer means, sample code and the cost of daily checks.

·

·

Cover: Next Hearing Date API, 100 cases in one call, 1 to 100 CNRs per request, Rs 0.10 per CNR at the Enterprise rate and Rs 0.30 on Pay As You Go

Next Hearing Date API: check 100 cases against upcoming cause lists in one call

The CNR batch check of the eCourtsIndia API takes up to 100 case numbers and tells you, for each one, whether it is on an upcoming district or taluka court cause list and, if so, the date, court, courtroom, item number and purpose.

POST /api/partner/causelist/cnr/batch costs ₹0.10 per distinct CNR at the Enterprise base rate or ₹0.30 on Pay As You Go. Duplicates and blanks are not billed.

New accounts get ₹200 in free API credits with no card. Prices from ecourtsindia.com/api/pricing, read 15 November 2026.

Last updated: 15 November 2026

Key takeaways

  • Built for portfolios: send 1 to 100 CNRs in one request and get the next listing for each, without opening any case.
  • Three possible answers: listed (with date and courtroom), not listed, or no cause-list data because the court is a High Court, the Supreme Court or a tribunal. Treat the last two differently.
  • Cheap enough to run daily: 1,000 cases checked every day for a month cost ₹3,000 at the base rate or ₹9,000 on Pay As You Go.
  • Pairs with refresh: when a case is not listed and its own next date has passed, refresh the case from the court rather than assuming nothing is happening.
  • Already have cases in the eCourts Services app? Our guide to bulk CNR upload shows how to bring them across.

What question does this endpoint answer?

“Which of my cases is coming up, when, and where?” for a whole list of cases at once.

Every case in an Indian court has a CNR. A lawyer, a company’s legal team or a lender usually holds a list of them. The usual way to know what is coming up is to open each case on the court portal, read the next date, then check the court’s cause list on the morning itself. The batch check skips both steps for district and taluka courts. It reads the cause lists we already hold, roughly 30 days ahead, and matches your CNRs against them.

If you do not know the CNRs and want to search the board by advocate, party or judge instead, use Cause List Search. If you want the full case record, use Case Detail, documented in the API reference.

What does a batch check return?

We sent four CNRs on 15 November 2026: three cases in Lucknow district courts and one Delhi High Court suit. Three came back listed and one came back with no cause-list data. The Lucknow cases belong to private parties on one side, so their CNRs are masked here.

POST /api/partner/causelist/cnr/batch
{"cnrs": ["UPLK04........2017", "UPLK06........2024",
          "UPLK05........2014", "DLHC010813232015"]}
CNRAnswerNext listingCourt and courtroomPurpose
UPLK04……..2017Listed18 November 2026, item 1Additional Court No. 5 (N.I. Act), courtroom 83Evidence
UPLK05……..2014Listed19 November 2026, item 43ACJ (Senior Division) Court No. 24Not stated
UPLK06……..2024Listed20 November 2026, item 21ACJ (Junior Division) Court No. 33, courtroom 61Not stated
DLHC010813232015No cause-list dataNone returnedDelhi High CourtHigh Court lists are not in the dataset
Live CNR batch check through the eCourts MCP on 15 November 2026. Three Lucknow district court cases and one Delhi High Court suit; private parties’ CNRs masked.

Cost of that call: four distinct CNRs at ₹0.30 each on Pay As You Go, ₹1.20 in all, or ₹0.40 at the base rate. The Section 138 complaint listed for evidence is the kind of entry that needs action: someone has to make sure the complainant’s witness is in court. Our Section 138 tracking guide shows how lenders build that into a workflow.

How should your code treat each answer?

“Not listed” and “no cause-list data” look similar in a response and mean very different things.

  • Listed: act on it. Send the date, courtroom and item number to the advocate and the client.
  • Not listed, district or taluka court: nothing is on the lists we hold for that court. Read the case’s own next hearing date. If that date has already passed and the case is still pending, refresh the case; courts sometimes publish the new date late. If the judge is on leave, the board itself can move; see what happens to your hearing when a judge is on leave.
  • No cause-list data: the case is in a High Court, the Supreme Court or a tribunal, whose lists are not in this dataset. It does not mean the case has no hearing. Use the next hearing date in the case detail, as our High Court case status guide explains for each court.
import os, requests

BASE = "https://webapi.ecourtsindia.com"
H = {"Authorization": f"Bearer {os.environ['ECI_TOKEN']}"}

def check(cnrs):
    out = []
    for i in range(0, len(cnrs), 100):                     # 100 per call
        r = requests.post(f"{BASE}/api/partner/causelist/cnr/batch", headers=H,
                          json={"cnrs": cnrs[i:i + 100]}, timeout=60)
        r.raise_for_status()
        out += r.json()["data"]
    return out

district = lambda cnr: not (cnr.startswith("SCIN") or "HC" in cnr[:4])
for row in check(my_cnrs):
    if row["hasCauselist"]:
        n = row["nextListing"]
        print(row["cnr"], n["date"], n["courtName"], "item", n["listingNo"], n.get("listingFor"))
    elif district(row["cnr"]):
        print(row["cnr"], "not listed: check nextHearingDate, refresh if past")
    else:
        print(row["cnr"], "no cause-list data for this court: use case detail")

The district test in that sketch is deliberately simple; tribunal CNRs have their own prefixes, so in production keep a court-type field per CNR from the case detail rather than guessing from the prefix.

What does it cost to run every day?

Checking 1,000 cases every day for a month is 30,000 checks: ₹3,000 at the base rate or ₹9,000 on Pay As You Go, before GST.

Two ways to spend less. Check pending cases only; disposed cases will not be listed again unless restored. And check most cases weekly but cases with a hearing in the next seven days daily. For context, LegalKart’s API page lists cause list by CNR at ₹2.00 per hit (read on the same date), so a daily 1,000-case check there would be ₹60,000 a month at that price.

How does it fit with refresh and case detail?

Use the batch check as the cheap daily signal, the case detail as the source of truth, and refresh only when the two disagree.

CallUse it forPrice (PAYG / Enterprise)
CNR batch checkDaily: is anything coming up in district courts?₹0.30 / ₹0.10 per CNR
Case DetailThe full record, including nextHearingDate for High Court and tribunal cases₹1.50 / ₹0.50
Case Refresh / Bulk RefreshWhen nextHearingDate is in the past on a pending case₹0.15 / ₹0.05 per CNR
Order + AIWhen a hearing has happened and you need to know what the court did₹7.50 / ₹2.50
How the cause list batch check combines with other eCourtsIndia API calls. Prices from ecourtsindia.com/api/pricing, read 15 November 2026.

After a listed date passes, the useful question becomes “what happened?”. That is a job for the order endpoints; our Court Order Summary API guide shows how to read the newest order with a summary you can check. For the full refresh lifecycle, see from scraping to production.

Who uses it?

  • Corporate legal teams running a daily list of upcoming hearings across every pending matter. Our general counsel portfolio playbook does this on the MCP.
  • Banks, NBFCs and collection agencies briefing local counsel on recovery suits and cheque-bounce complaints before each date.
  • Law firms and practice-management software that show a “this week” view to advocates and send reminders to clients.
  • Individual litigants who do not need code at all: the website’s case alerts send the next listing to email and WhatsApp, and our case status guide explains the free routes.

Limits to plan for

  • 1 to 100 CNRs per request. More than 100 returns 400 BATCH_SIZE_EXCEEDED; a request with no usable CNR returns 400 INVALID_CNR.
  • Billing is per distinct CNR processed. Duplicates and blanks in the same request are ignored.
  • District and taluka courts only, about 30 days ahead.
  • The partner API allows 100 requests a minute and 10 concurrent. A 10,000-case portfolio is 100 requests, which is the whole per-minute allowance, so spread a run that size over two or three minutes.

Sources and method

  • eCourtsIndia API docs, ecourtsindia.com/api/docs (CNR Check Batch, errors, rate limits), read 15 November 2026.
  • eCourtsIndia API pricing, ecourtsindia.com/api/pricing, read 15 November 2026.
  • Live call through the eCourts MCP on 15 November 2026: check_cnr_causelist on four CNRs (three Lucknow district court cases and DLHC010813232015).
  • LegalKart API services page, legalkart.com/api-services, read 15 November 2026.

Frequently asked questions

How can I check the next hearing date for many cases at once?

Use the eCourtsIndia CNR batch check, POST /api/partner/causelist/cnr/batch, with up to 100 CNRs per request. For each district or taluka court case it returns whether the case is listed and the date, court, courtroom, item number and purpose. It costs ₹0.10 per CNR at the base rate. See the API docs.

Why does a High Court case come back with no cause-list data?

Because High Court, Supreme Court and tribunal cause lists are not in the dataset. That answer means we hold no list for that court, not that there is no hearing. Read the next hearing date from the case detail instead, as our High Court case status guide explains.

What should I do when a case is not listed?

For a district or taluka court case, check the case’s own next hearing date. If that date has passed and the case is still pending, refresh the case from the court, because the new date may not have been published to our copy yet. If the case is disposed, it will not appear on lists.

How much does a daily hearing check cost for 1,000 cases?

About 30,000 checks a month: ₹3,000 at the Enterprise base rate of ₹0.10 per CNR, or ₹9,000 on Pay As You Go at ₹0.30, before GST. Duplicate CNRs in a request are not billed.

Can I search cause lists without knowing the CNR?

Yes. Cause List Search finds listings by advocate, litigant, judge, court or date and returns the CNR for each row. Our Cause List API guide covers the filters.

Is there a free way to get hearing reminders?

Yes. On ecourtsindia.com you can track cases and turn on case alerts that send the next listing to email and WhatsApp. Our guide to enabling case alerts has the steps.

Important: This guide describes the eCourtsIndia API, made by Billion Insights Ventures Pvt. Ltd., the company that publishes this blog. It is not legal advice. API data is a copy of public court records as read on the stated date and is not a certified copy. A name match is not identity, a pending case is not guilt, and a disposed case is a status, not an outcome. Prices, limits and examples were checked on 15 November 2026 and can change. eCourtsIndia is a private legal-technology platform and is not affiliated with any court, the e-Committee of the Supreme Court or the Government of India. Found an error? Write to support@ecourtsindia.com.

Send the CNRs of your ten busiest cases and see which come up this fortnight.

eCourtsIndia is a private legal-technology platform. It is not affiliated with, associated with, or endorsed by the Government of India, the Supreme Court of India or its e-Committee, or any court. Official case information is published on ecourts.gov.in. Always verify details against official court records or certified copies. This article is general information, not legal advice. Spotted an error? Write to support@ecourtsindia.com.

Search 35 crore+ Indian court case records, free

One search across the Supreme Court, all 25 High Courts, district courts and 18 tribunal and commission types. Hearing alerts, AI summaries and an API for developers.