Nic APInclat.nic.in ↗
Access recent NCLAT judgments and orders from the Principal Bench (New Delhi) and Chennai Bench. Retrieve case titles, order dates, coram, and PDF URLs via one API.
What is the Nic API?
The NCLAT API exposes one endpoint — list_judgments — that returns up to the last 14 days of final orders and judgments from India's National Company Law Appellate Tribunal. Each record surfaces 10 fields including case number, case title with party names, bench location, order date, coram composition, and a direct PDF reference URL, covering both the New Delhi Principal Bench and the Chennai Bench.
curl -X GET 'https://api.parse.bot/scraper/c7ccabe4-6b69-41a2-a610-bc69b645fb48/list_judgments?page=1&location=delhi&page_size=15' \ -H 'X-API-Key: $PARSE_API_KEY'
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 nclat-nic-in-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: NCLAT SDK — bounded, re-runnable; every call capped."""
from parse_apis.nclat_nic_in_api import Nclat, Bench, InvalidInput
client = Nclat()
# List latest Delhi judgments — limit= caps TOTAL items fetched.
for judgment in client.judgments.list(location=Bench.DELHI, limit=3):
print(judgment.case_title, judgment.order_date, judgment.bench)
# Fetch a single recent Chennai judgment with .first()
item = client.judgments.list(location=Bench.CHENNAI, limit=1).first()
if item:
print(item.case_no, item.order_type, item.coram)
print("PDF:", item.pdf_url)
# Typed error handling around a call with invalid input
try:
for j in client.judgments.list(location=Bench.DELHI, limit=2):
print(j.filing_number, j.case_type, j.status)
except InvalidInput as e:
print("invalid input:", e)
print("exercised: judgments.list")
Retrieve recent NCLAT judgments and final orders from the last 14 days, sorted most-recent-first. Each item includes case title with party names, case number, order date, bench location, coram (bench composition), and a PDF reference URL. Results are paginated client-side from a single upstream fetch of the rolling 14-day window.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for client-side pagination over the 14-day result set. |
| location | string | NCLAT bench location. |
| page_size | integer | Number of items per page (1–50). |
{
"type": "object",
"fields": {
"page": "current page number",
"items": "array of judgment records with case_no, case_type, case_title, bench, order_date, order_type, coram, pdf_url, filing_number, status",
"total": "total number of judgments in the 14-day window",
"location": "bench location used for this query",
"page_size": "items per page",
"total_pages": "total number of pages"
},
"sample": {
"data": {
"page": 1,
"items": [
{
"bench": "New Delhi",
"coram": "Hon'ble Justice Yogesh Khanna (Officiating Chairperson) , Hon'ble Mr. Barun Mitra (Member (Technical)) , Hon'ble Mr. Ajai Das Mehrotra (Member (Technical)) ,",
"status": "Disposed",
"case_no": "538/ND/2022",
"pdf_url": "https://nclat.nic.in/display-board/view_order?filing_no=9910138000612022&order_date=2026-07-24&order_type=J&bench_name=delhi",
"case_type": "IA",
"case_title": "Vovid Solutions Pvt. Ltd. & Ors. VS Mukesh Jain & Ors.",
"order_date": "2026-07-24",
"order_type": "Final Order /Judgement",
"filing_number": "9910138000612022"
}
],
"total": 112,
"location": "delhi",
"page_size": 10,
"total_pages": 12
},
"status": "success"
}
}About the Nic API
What the API Returns
The list_judgments endpoint delivers a paginated list of recent NCLAT judgments and final orders from a rolling 14-day window. Each item in the items array includes case_no, case_type, case_title (with party names), bench, order_date, order_type, coram, pdf_url, filing_number, and status. Results are sorted most-recent-first, giving you immediate access to the latest appellate decisions affecting company law matters in India.
Filtering and Pagination
The location parameter lets you restrict results to a specific bench — either the Principal Bench in New Delhi or the Chennai Bench. Pagination is controlled via the page and page_size parameters (1–50 items per page). The response envelope always includes total, total_pages, page, and page_size so you can build accurate pagination UI or iterate programmatically over the full result set.
Coverage and Freshness
Data reflects judgments published within the last 14 days on the official NCLAT website at nclat.nic.in. The pdf_url field points directly to the order document, allowing downstream consumers to fetch and parse the full text of the judgment. The coram field identifies the bench composition by name, which is useful for tracking decisions by specific judges or benches over time.
The Nic API is a managed, monitored endpoint for nclat.nic.in — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when nclat.nic.in 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 nclat.nic.in 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 daily NCLAT orders relevant to a specific company by filtering
case_titlefor party names. - Build a legal alert system that notifies counsel when new insolvency-related orders are published.
- Aggregate
pdf_urllinks for bulk download and full-text indexing of NCLAT judgments. - Track bench composition trends using the
coramfield across the New Delhi and Chennai benches. - Populate a legal research database with structured metadata:
case_no,order_date,order_type, andbench. - Audit filing timelines by correlating
filing_numberwithorder_dateacross the 14-day window.
| 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 | 100 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 NCLAT provide an official developer API?+
What does `list_judgments` actually return for each record?+
items array contains: case_no, case_type, case_title (with both party names), bench (New Delhi or Chennai), order_date, order_type, coram (the judges who heard the matter), pdf_url (a direct link to the order document), filing_number, and status.How far back does the judgment data go?+
list_judgments endpoint covers a rolling 14-day window from the current date. Orders older than 14 days are not returned. If you need a longer historical range, you can fork this API on Parse and revise it to extend the lookback period.Can I retrieve judgments from NCLAT benches other than New Delhi and Chennai?+
Does the API return the full text of the judgment or just metadata?+
pdf_url field pointing to the order document, but the API returns structured metadata only — not the extracted text of the judgment itself. You can fork this API on Parse and revise it to include a text-extraction endpoint that fetches and parses the linked PDF.