Gov APIgstat.gov.in ↗
Access GST Appellate Tribunal daily cause lists across 44 benches in India. Fetch locations, courts, and scheduled hearings by date, location, and court ID.
What is the Gov API?
This API covers the GST Appellate Tribunal (GSTAT) cause list portal across 44 bench locations in India, exposed through 3 endpoints. The get_cause_list endpoint returns scheduled hearings for a given date, location, and court, including case numbers, party names, hearing purpose, quorum, time slots, and representative details. Two supporting endpoints — list_locations and get_courts — provide the IDs needed to query hearings.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/2a101750-4782-4a80-8b25-187efa949893/list_locations' \ -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 gstat-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: GSTAT Cause List SDK — bounded, re-runnable; every call capped."""
from parse_apis.gstat_gov_in_api import Gstat, ParseError
client = Gstat()
# List available bench locations across India.
for loc in client.locations.list(limit=3):
print(loc.id, loc.name)
# Pick a location and list its courts.
delhi = client.location(id="1")
for court in delhi.courts.list(limit=3):
print(court.id, court.name)
# Fetch the cause list for a specific court and date.
for cause in delhi.causes.list(court_id="1", date="2026-07-22", limit=3):
print(cause.case_no, cause.parties, cause.purpose)
# Typed error handling around a call that can fail.
try:
for c in client.location(id="999").courts.list(limit=1):
print(c.name)
except ParseError as e:
print(f"error: {e}")
print("exercised: locations.list / courts.list / causes.list")
Returns all GSTAT bench locations with their numeric IDs. These IDs are used as input to get_courts and get_cause_list. The list is stable (44 benches across India) and changes only when new benches are constituted.
No input parameters required.
{
"type": "object",
"fields": {
"locations": "array of location objects with id and name"
},
"sample": {
"data": {
"locations": [
{
"id": "1",
"name": "Delhi (PB)"
},
{
"id": "40",
"name": "Agra"
},
{
"id": "21",
"name": "Mumbai"
}
]
},
"status": "success"
}
}About the Gov API
Endpoints and Data Covered
list_locations returns the full set of GSTAT bench locations — currently 44 across India — each with a numeric id and name. These IDs are the entry point for all other queries. The list is stable and updates only when new benches are constituted. get_courts takes a location_id and returns the courts available at that bench, typically between one and five numbered courts plus a Registrar Court, each with its own id and name.
Cause List Detail
get_cause_list is the primary data endpoint. It requires a date (ISO format YYYY-MM-DD), a court_id, and a location_id. The response includes paginated causes records, each containing the case number, filing number, petitioner and respondent names, hearing purpose, scheduled time, quorum composition, and details of authorised representatives. Pagination is handled via page, limit, total_pages, and total_records fields, and results are auto-iterated across pages.
Coverage and Freshness
The cause list reflects daily schedules as published by the Tribunal. Data is specific to the date passed — there is no range query across multiple dates in a single call. To retrieve hearings for multiple dates or benches, callers must loop over list_locations output and issue separate get_cause_list calls per date, court, and location combination.
The Gov API is a managed, monitored endpoint for gstat.gov.in — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when gstat.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 gstat.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?+
- Alert lawyers and tax practitioners when a specific case number appears on the cause list for a scheduled hearing date
- Aggregate daily hearing schedules across multiple GSTAT bench locations for a litigation management dashboard
- Track quorum composition changes across benches over time using the quorum field in cause records
- Build a case-status monitor that maps filing numbers to upcoming hearing purposes and times
- Generate automated daily briefings listing all hearings at a chosen court by filtering on location_id and court_id
- Research hearing frequency and workload distribution across GSTAT's 44 benches using total_records per location
| 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 gstat.gov.in provide an official developer API?+
What fields does get_cause_list return for each scheduled hearing?+
causes array includes the case number, filing number, petitioner and respondent names, hearing purpose, scheduled time, quorum details, and authorised representative information. Pagination metadata — page, limit, total_pages, and total_records — is returned alongside the records.Can I query cause lists across a date range in a single call?+
get_cause_list accepts a single date value per call. To cover a date range, you must issue one call per date, court, and location combination. You can fork this API on Parse and revise it to add a date-range iteration wrapper endpoint.Does the API expose historical orders, judgments, or case documents?+
How often does the list of bench locations change?+
list_locations returns a stable set of 44 benches. The list changes only when the Tribunal constitutes new benches, which is infrequent. Callers can cache the output and refresh periodically rather than fetching it on every request.