Court Case Search by Name API, across India

Example

curl -X POST https://verified.realestate/api/v1/tools/court_cersai \
  -H "Authorization: Bearer $LANDLENS_KEY" \
  -H "Content-Type: application/json" \
  -d '{"subject":"ecourt","owner_name":"T Ganesalingam"}'

{
  "ok": true,
  "status": "proposal",
  "data": {
    "proposal": true,
    "action": "ecourt_search",
    "label": "Court case search by name: T Ganesalingam",
    "params": { "name": "T Ganesalingam" },
    "cost": 2,
    "source": "eCourts case registry",
    "note": "Name-based search across India. Common names can return unrelated cases, results need manual verification. Charged when the search completes, whether or not cases are found. A failed search is not charged."
  },
  "credits_quoted": 0,
  "credits_charged": 0,
  "credits_waived": 0,
  "next": {
    "tool": "approve_action",
    "arguments": { "action": "ecourt_search", "params": { "name": "T Ganesalingam" } }
  }
}

A real quote from the API, with balance_after and request_id left out. Approving it runs the search.

What it returns

The first call returns a quote, with status proposal. Send its next block to approve_action within 30 minutes; the approved search answers in the same request.

Inputs

The JSON body of the POST is the arguments. Only subject is required by the schema; this search also needs owner_name. A call without it answers not_found and nothing is quoted.

Code

Set LANDLENS_KEY to your key. In an AI app, connect https://verified.realestate/mcp once and ask in plain words instead. In Postman, download this API's collection, import it (File, Import) and set apiKey; the quote, the approval and the job status are chained for you.

curl -X POST https://verified.realestate/api/v1/tools/court_cersai \
  -H "Authorization: Bearer $LANDLENS_KEY" \
  -H "Content-Type: application/json" \
  -d '{"subject":"ecourt","owner_name":"T Ganesalingam"}'

import os, requests

r = requests.post(
    "https://verified.realestate/api/v1/tools/court_cersai",
    headers={"Authorization": f"Bearer {os.environ['LANDLENS_KEY']}"},
    json={
        "subject": "ecourt",
        "owner_name": "T Ganesalingam"
    },
    timeout=120,
)
body = r.json()
print(body["status"], body["credits_charged"], body["data"])

const res = await fetch("https://verified.realestate/api/v1/tools/court_cersai", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.LANDLENS_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "subject": "ecourt",
    "owner_name": "T Ganesalingam"
  }),
});
const body = await res.json();
console.log(body.status, body.credits_charged, body.data);

Search court cases across India for T Ganesalingam, the seller of survey 119, and tell me which ones look like him.

Responses

Every answer has the same envelope. What status can say for this call:

Where the data comes from

Who uses it

Limits and good practice

• A name is not a person. Common names return cases of many people; check parties, court and place before treating a hit as your seller's.
• One approved search returns the first 50 matches. total_hits says how many there are in all; narrow the name rather than relying on the first page for a common one.
• The search is charged once it completes, even when no case comes back, because the answer "no cases" is what was paid for. Only a search that fails is refunded.
• Revenue court petitions are in a separate register. Search them by survey number with subject revenue_court.

Pricing

Questions

Related APIs