The corpus,
over REST.
Search, analysis, notice replies and trends from your own application. JSON in, JSON out, citations attached.
$
200 OK · 184 results · 0.9s
{
"title": "ABC Infra Pvt. Ltd. v. XYZ Engineering Ltd.",
"court": "HC-DEL",
"status": "pending",
"next_hearing": "2026-11-04"
}
77 endpoints. One key. Credits only on success.
/v1/searchSearch & Discovery · 3 endpoints · 1 live, 2 coming soon
/v1/judgments/{doc_id}Judgments & Documents · 6 endpoints · 3 live, 3 coming soon
/v1/judgments/{doc_id}/citationsCitations & Precedent Mapping · 6 endpoints · coming soon
/v1/ai/searchAI Research (RAG) · 6 endpoints · coming soon
/v1/cases/searchCase Status & Litigation Tracking · 7 endpoints · 6 live, 1 coming soon
/v1/actsActs, Rules & Notifications · 5 endpoints · coming soon
/v1/analytics/judges/{judge_id}Analytics · 5 endpoints · 4 live, 1 coming soon
/v1/courtsMaster / Reference Data · 3 endpoints · live
/v1/feeds/updatesBulk Data, Feeds & Webhooks · 4 endpoints · live
/v1/account/usageAccount & Platform · 3 endpoints · live
/api/client/registerMonetization · Client · 16 endpoints · live
/api/admin/dashboardMonetization · Admin · 12 endpoints · live
/api/webhooks/payments/{provider}Monetization · Payments · 1 endpoint · live
53 of 77 endpoints are live today. Endpoints marked coming soon are routed with their contracts and answer 501 NOT_AVAILABLE - never billed - until judgment text, citations and statutes are indexed. Full reference, code samples and playground →
A search, in three languages.
import os, requests
resp = requests.get(
"https://api.nyayakosh.ai/v1/cases/search",
headers={"Authorization": f"Bearer {os.environ['NK_API_KEY']}"},
params={"court": "HC-DEL", "party": "ABC Infra", "status": "pending"},
)
body = resp.json()
for case in body["data"]:
print(case["cnr"], case["title"], case["next_hearing"])
const params = new URLSearchParams({ court: "HC-DEL", party: "ABC Infra" });
const res = await fetch(`https://api.nyayakosh.ai/v1/cases/search?${params}`, {
headers: { Authorization: `Bearer ${process.env.NK_API_KEY}` },
});
const { success, data, error } = await res.json();
if (!success) throw new Error(error.code);
curl -G https://api.nyayakosh.ai/v1/cases/search \
-H "Authorization: Bearer $NK_API_KEY" \
-d court=HC-DEL --data-urlencode "party=ABC Infra" -d status=pending
{
"success": true,
"data": [
{
"cnr": "DLHC011234562025",
"case_id": "nk_case_abvnl6xkb4rq…",
"court": "HC-DEL",
"case_type": "ARB.A.",
"title": "ABC Infra Pvt. Ltd. v. XYZ Engineering Ltd.",
"status": "pending",
"next_hearing": "2026-11-04"
}
],
"meta": { "request_id": "req_8h2k3lq0", "page": 1, "total": 23, "credits_used": 1 }
}
How it behaves in production.
Bearer tokens
Authorization: Bearer or X-API-Key. nk_test_ sandbox keys are never billed; nk_live_ keys use your plan's credits. Scopes, IP allowlists, expiry and rotation with an overlap window.
Rate limits & credits
Limits are reported on every response in X-RateLimit-Remaining; a limited call returns 429 with Retry-After. Only successful calls consume credits; X-Credits-Remaining shows what is left this month.
Idempotency
Send an Idempotency-Key on any POST. A retry with the same key returns the original response instead of doing the work twice.
| Status | Code | Meaning |
|---|---|---|
400 | INVALID_PARAM | A field is missing or malformed. The response names the field. |
401 | API_KEY_MISSING / API_KEY_INVALID / API_KEY_REVOKED / API_KEY_EXPIRED / IP_NOT_ALLOWED | Missing or invalid credentials. |
402 | SUBSCRIPTION_EXPIRED / SUBSCRIPTION_PAST_DUE / INSUFFICIENT_CREDITS | Payment or plan action needed. |
403 | PRODUCT_NOT_IN_PLAN / ENDPOINT_NOT_PERMITTED / ACCOUNT_SUSPENDED | Not authorised for this API. |
404 | NOT_FOUND | No case or document with that id. |
422 | INVALID_FILTER | Valid request, unknown or not-yet-available filter value. |
429 | RATE_LIMITED / QUOTA_EXCEEDED | Slow down; respect Retry-After. |
501 | NOT_AVAILABLE | Documented, data not indexed yet. Not billed. |
5xx | INTERNAL / SOURCE_UNAVAILABLE | Our side. Safe to retry with backoff and the same Idempotency-Key. |
Be told when the law moves.
Watch cases and parties. When a hearing date moves, an order is uploaded, a status changes or a new case names a watched party, we post the event — signed with HMAC-SHA256 and retried with backoff for 24 hours.
Webhook reference{
"event": "case.hearing_updated",
"id": "evt_5f2c9a1b7e3d4c60",
"created_at": "2026-10-19T06:12:44Z",
"data": {
"cnr": "DLHC011234562025",
"title": "ABC Infra Pvt. Ltd. v. XYZ Engineering Ltd.",
"previous": "2026-10-27",
"next_hearing": "2026-11-04"
}
}
Building on it?
Pick an API plan, pay online and create your keys in minutes from your developer dashboard. Need higher volume? Talk to us.
Get an API key