livelaw.in APIlivelaw.in ↗
Access Supreme Court judgments, High Court news, legal digests, and category articles from LiveLaw.in via 7 structured endpoints with year and category filtering.
curl -X GET 'https://api.parse.bot/scraper/7e47d148-c39b-4769-86db-8d0c424a52dd/get_sc_judgments?year=2026&max_pages=5' \ -H 'X-API-Key: $PARSE_API_KEY'
Fetch paginated list of Supreme Court judgments for a specific year. Iterates through listing pages and filters by year. Returns all matching judgments up to the max_pages limit.
| Param | Type | Description |
|---|---|---|
| year | integer | The year of judgments to extract. |
| max_pages | integer | Maximum number of listing pages to scan. |
{
"type": "object",
"fields": {
"year": "integer — the requested year",
"count": "integer — number of judgments found",
"judgments": "array of judgment objects with title, url, summary, date, author, year"
},
"sample": {
"data": {
"year": 2026,
"count": 24,
"judgments": [
{
"url": "https://www.livelaw.in/sc-judgments/2026-livelaw-sc-445-nandi-infrastructure-corridor-enterprises-ltd-anr-versus-b-gurappa-naidu-ors-532605",
"date": "",
"year": 2026,
"title": "2026 LiveLaw (SC) 445 | NANDI INFRASTRUCTURE CORRIDOR ENTERPRISES LTD. & ANR. VERSUS B. GURAPPA NAIDU & ORS",
"author": "",
"summary": "Supreme Court Summarises Principles For Exercise Of Article 227 Jurisdiction"
}
]
},
"status": "success"
}
}About the livelaw.in API
The LiveLaw.in API exposes 7 endpoints covering Supreme Court judgments, High Court news, legal digests, and category-specific articles from India's LiveLaw publication. The get_sc_judgments endpoint lets you retrieve paginated judgment listings filtered by year, returning structured objects with title, URL, summary, date, and author. The API covers both free and premium content detection, and supports court-specific filtering down to individual High Court slugs.
Supreme Court Judgments
The get_sc_judgments endpoint accepts a year integer and a max_pages limit, then returns a judgments array where each object includes title, url, summary, date, author, and year. The response also includes a top-level count field so you know how many matching judgments were found without iterating the array. This is the primary endpoint for building year-scoped judgment databases or tracking citation trends over time.
Article Detail and Premium Status
get_article_detail accepts either a slug (e.g., sc-judgments/2025-livelaw-sc-1-example-case-title) or a full URL and returns the body text, title, url, and an is_premium boolean. When is_premium is true, body may be empty — the field signals paywalled content rather than a fetch failure. This distinction matters when building pipelines that need to separate freely available text from gated material.
High Courts and Category Listings
get_high_court_news returns paginated articles across all Indian High Courts. For court-specific results, get_high_court_by_name takes a court_slug such as bombay-high-court or allahabad-high-court and returns items scoped to that court. get_category_articles works similarly — pass a category slug like arbitration, consumer-cases, or ibc alongside a page number to retrieve topically filtered article lists. All three endpoints return the same article object shape: title, url, summary, date, author, and year.
Digests and Top Stories
get_digests retrieves weekly, monthly, and quarterly legal roundups from various courts, useful for summarising judicial activity over a period. get_top_stories returns the current top stories with pagination. Both endpoints use the same paginated items array structure, making it straightforward to consume them with identical parsing logic.
- Build a year-wise Supreme Court judgment archive using
get_sc_judgmentswith theyearparameter - Flag premium vs. free content in a legal research tool using the
is_premiumfield fromget_article_detail - Monitor High Court activity for a specific court by polling
get_high_court_by_namewith the relevantcourt_slug - Aggregate weekly and monthly legal digests for an automated legal newsletter using
get_digests - Filter arbitration or IBC case coverage with
get_category_articlesusing category slugs likearbitrationoribc - Track author output across Supreme Court and High Court reporting using the
authorfield returned by all listing endpoints - Surface the latest Indian legal developments in a news aggregator by paginating
get_top_stories
| 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 | 250 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 LiveLaw.in have an official developer API?+
What does `get_sc_judgments` return and how do I narrow results to a specific year?+
judgments array where each object includes title, url, summary, date, author, and year, plus a top-level count. Pass the year integer parameter to filter results. Use max_pages to cap how many listing pages are scanned, which controls response time and volume.How does the API handle paywalled LiveLaw articles?+
get_article_detail endpoint returns an is_premium boolean. When it is true, the body field will typically be empty. The API surfaces the paywall status so your application can handle gated content explicitly rather than treating an empty body as an error.Does the API cover Tribunal or District Court decisions, not just Supreme Court and High Courts?+
get_sc_judgments and High Court news via get_high_court_news and get_high_court_by_name, plus category-based articles and digests. It does not include dedicated endpoints for Tribunal or District Court decisions. You can fork this API on Parse and revise it to add the missing endpoint.Are there any known limitations with pagination across the listing endpoints?+
get_top_stories, get_high_court_news, get_digests, get_category_articles) accept a page integer but do not return total page counts in the response. For get_sc_judgments, the max_pages parameter bounds the scan depth. You will need to implement stop logic in your client — for example, halting when an items array returns empty — rather than relying on a declared total.