Court Case Status Lookup
Risk & ComplianceTrack a specific case by CNR or case number: status, next hearing and orders.
Given a CNR number or court, case type, number and year, return the current stage, parties, next hearing date and the orders passed, so legal and collections teams monitor litigation without manual portal visits.
Endpoint
POST
https://app.emver.io/api/sandbox/v1/case-status-lookup
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
Accept: application/json
Request parameters
| Field | Type | Description |
|---|---|---|
cnr_number
optional
|
string | CNR number |
court
optional
|
string | Court (when no CNR) |
case_number
optional
|
string | Case number |
year
optional
|
number | Case year |
Example request
cURL
curl -X POST https://app.emver.io/api/sandbox/v1/case-status-lookup \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"cnr_number": "string",
"court": "string",
"case_number": "string",
"year": 0
}'
import requests
response = requests.post(
"https://app.emver.io/api/sandbox/v1/case-status-lookup",
headers={
"Authorization": "Bearer YOUR_API_KEY",
"Accept": "application/json",
},
json={
"cnr_number": "string",
"court": "string",
"case_number": "string",
"year": 0
},
timeout=60,
)
response.raise_for_status()
data = response.json()
const response = await fetch("https://app.emver.io/api/sandbox/v1/case-status-lookup", {
method: "POST",
headers: {
"Authorization": "Bearer YOUR_API_KEY",
"Content-Type": "application/json",
"Accept": "application/json",
},
body: JSON.stringify({
"cnr_number": "string",
"court": "string",
"case_number": "string",
"year": 0
}),
});
const data = await response.json();
$response = Http::withToken('YOUR_API_KEY')
->acceptJson()
->post('https://app.emver.io/api/sandbox/v1/case-status-lookup', {
"cnr_number": "string",
"court": "string",
"case_number": "string",
"year": 0
});
$data = $response->json();
Replace YOUR_API_KEY and the placeholder values. Use the switch above to see production URLs.
Response
Structure · 200
{
"status": INTEGER,
"message": STRING,
"data": {
"case_title": STRING,
"stage": STRING,
"parties": ARRAY,
"next_hearing": DATE,
"orders": ARRAY
}
}
Example · 200
{
"status": 200,
"message": "string",
"data": {
"case_title": "string",
"stage": "string",
"parties": "string",
"next_hearing": "YYYY-MM-DD",
"orders": "string"
}
}
Error · 4xx / 5xx
{
"status": INTEGER,
"message": STRING
}
See Errors & status codes for what each status means and which calls are billed.
About this API
Where Court & Criminal Records Check searches by person, this API tracks a known case. Poll it or subscribe to changes to be told when a hearing is listed or an order is uploaded.
Typical uses
- Recovery and collections. Monitor cases against defaulters.
- In-house legal. Portfolio-wide litigation tracking.
Questions
- Which courts are covered?
- District and high courts publishing through the national e-courts systems, plus tribunals that expose case status.