Gov APIgreentribunal.gov.in ↗
Access NGT judgments, orders, and case status data via the greentribunal.gov.in API. Search by bench, case title, and paginate through results.
What is the Gov API?
The greentribunal.gov.in API provides structured access to judgments and orders from India's National Green Tribunal (NGT) through a single list_orders endpoint that returns up to 6 fields per case record. Each result includes the case number, party names, order date, current case status, bench assignment, and a direct URL to the full order detail. Results are sorted by most recent order date, making it straightforward to track new NGT activity.
curl -X GET 'https://api.parse.bot/scraper/90ecbe08-5f95-4a01-860b-df7616b58636/list_orders?page=1&bench=principal&search_term=vs' \ -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 greentribunal-gov-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: NGT SDK — bounded, re-runnable; every call capped."""
from parse_apis.greentribunal_gov_in_api import NGT, Bench, InvalidInput
client = NGT()
# List recent orders from the Principal Bench (most recent first)
for order in client.orders.list(bench=Bench.PRINCIPAL, limit=3):
print(order.case_number, order.party_name, order.order_date)
# Narrow to a specific bench and search term
item = client.orders.list(bench=Bench.WESTERN, search_term="pollution", limit=1).first()
if item:
print(item.bench, item.case_status, item.detail_url)
# Typed error handling
try:
for order in client.orders.list(bench=Bench.EASTERN, limit=2):
print(order.diary_number, order.order_date, order.case_status)
except InvalidInput as e:
print("bad input:", e)
print("exercised: orders.list")
Search and list latest judgments and orders from the NGT case status system. Results are ordered by most recent order date first, returning up to 20 items per page. Searches case titles using the provided search term across the selected bench. The search covers all case types including Original Applications, IAs, Appeals, and Execution Applications.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination (1-based). |
| bench | string | NGT bench/zone to search. |
| search_term | string | Free text keyword to search in case titles. Use 'vs' to match virtually all cases (as most titles contain 'Applicant VS Respondent'). |
{
"type": "object",
"fields": {
"page": "current page number",
"bench": "bench filter applied",
"items": "array of case/order records with bench, case_number, party_name, order_date, case_status, and detail_url",
"search_term": "search term used",
"total_pages": "total number of pages available"
},
"sample": {
"page": 1,
"bench": "principal",
"items": [
{
"bench": "NEW DELHI (PRINCIPAL BENCH)",
"detail_url": "https://www.greentribunal.gov.in/caseDetails/DELHI/0701114013012026/vs",
"order_date": "13-07-2026",
"party_name": "ARVIND GOEL VS STATE OF PUNJAB",
"case_number": "IA No. 520/2026 / DELHI",
"case_status": "DISPOSED",
"filing_date": "09-07-2026",
"diary_number": "070111401301/2026"
}
],
"search_term": "vs",
"total_pages": 148
}
}About the Gov API
What the API Returns
The list_orders endpoint queries the NGT case status system and returns paginated arrays of case and order records. Each item in the items array carries six fields: bench (the NGT zone that heard the case), case_number, party_name (the case title, typically formatted as Applicant vs Respondent), order_date, case_status (e.g. pending, disposed), and detail_url pointing to the full order on the NGT website. The response also echoes back the bench filter, search_term, current page, and total_pages so you can walk through the full result set.
Filtering and Pagination
Two optional parameters control what the endpoint returns. The bench parameter narrows results to a specific NGT zone — for example, the Principal Bench in New Delhi or regional benches in Chennai, Pune, Bhopal, or Kolkata. The search_term parameter performs a free-text match against case titles; since most NGT case titles contain the word 'vs', using that as a search term effectively retrieves a broad cross-section of cases across the selected bench. The page parameter (1-based) lets you walk through up to total_pages of results, with up to 20 records per page.
Coverage and Data Freshness
The API covers all case types handled by the NGT, including Original Applications, Appeal Cases, Execution Petitions, and Miscellaneous Applications. Results are ordered by most recent order_date first, so the first page of any bench query reflects the latest orders issued. Case titles typically follow the Applicant vs Respondent naming convention used in NGT filings.
The Gov API is a managed, monitored endpoint for greentribunal.gov.in — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when greentribunal.gov.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 greentribunal.gov.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 newly issued NGT orders for a specific bench by polling
list_orderswith a bench filter and checking the latestorder_datevalues. - Track the
case_statuschanges of environmental litigation cases involving a specific party by searching the party name insearch_term. - Build a database of NGT disposal rates by collecting
case_statusandorder_datefields across all benches over time. - Alert legal teams when new orders appear for cases matching a client's name using the
party_namefield from paginated results. - Aggregate
detail_urllinks from multiple bench queries to build a local archive of NGT order documents. - Research case distribution across NGT zones by querying each bench and counting records returned in
total_pages.
| 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 the National Green Tribunal provide an official developer API?+
What does the `bench` parameter accept, and how does it affect results?+
bench parameter filters results to a specific NGT zone. The NGT operates benches in New Delhi (Principal Bench), Chennai, Pune, Bhopal, and Kolkata. Omitting the parameter returns results without a bench restriction. Each response echoes back the bench value that was applied so you can verify the filter in use.Does the API return the full text of judgments or just metadata?+
case_number, party_name, order_date, case_status, bench, and a detail_url linking to the full order on the NGT website. The full judgment text is not included in the response. You can fork this API on Parse and revise it to follow the detail_url and extract full order text as an additional endpoint.Is there a way to filter cases by date range or case type?+
list_orders endpoint filters by bench and search_term only; results are always sorted by most recent order_date first, but no explicit date-range or case-type parameter is exposed. You can fork this API on Parse and revise it to add date-range or case-type filtering as additional parameters.How fresh is the case data returned by `list_orders`?+
order_date descending. Because the NGT updates its system when orders are issued, the first page of results for any bench query generally reflects recently posted orders. There is no guaranteed real-time SLA, and publication delays on the NGT's own system will be reflected in the data.