CERSAI Property Search API

Example

curl -X POST https://verified.realestate/api/v1/tools/court_cersai \
  -H "Authorization: Bearer $LANDLENS_KEY" \
  -H "Content-Type: application/json" \
  -d '{"subject":"cersai","district_name":"Kancheepuram","survey_number":"65","sub_division":"4B","lat":12.8421,"lng":80.031}'

{
  "ok": true,
  "status": "proposal",
  "data": {
    "proposal": true,
    "action": "cersai_search",
    "label": "CERSAI mortgage / charge search for survey 65 (covering sub-division 4B)",
    "params": {
      "owner_name": "",
      "district": "Kancheepuram",
      "city": "Kattankolathur SO",
      "pincode": "603203",
      "survey_no": "65",
      "sub_division": "4B",
      "plot_no": "",
      "door_no": ""
    },
    "cost": 2,
    "note": "Live national registry search, can take a few minutes. Charged only if the search completes. CERSAI files by the parent survey, so this searches the whole of survey 65 including sub-division 4B."
  },
  "credits_charged": 0,
  "next": { "tool": "approve_action", "arguments": { "action": "cersai_search", "params": { "...": "..." } } }
}

A real quote from the API, trimmed of request_id and balance. City and PIN code were worked out from the map point. Send params back exactly as quoted, blank fields included.

What it returns

The first call returns a quote, with status proposal. Send its next block to approve_action within 30 minutes; the search is queued and its result is read with job_status, from the status_url, or delivered to your callback_url. These are the fields of the delivered result (data.payload in job_status).

Inputs

The JSON body of the POST is the arguments. Only subject is required by the schema, but the registry needs a district, a city, a PIN code and one of survey, plot or door number.

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":"cersai","district_name":"Kancheepuram","survey_number":"65","sub_division":"4B","lat":12.8421,"lng":80.031}'

import os, requests

r = requests.post(
    "https://verified.realestate/api/v1/tools/court_cersai",
    headers={"Authorization": f"Bearer {os.environ['LANDLENS_KEY']}"},
    json={
        "subject": "cersai",
        "district_name": "Kancheepuram",
        "survey_number": "65",
        "sub_division": "4B",
        "lat": 12.8421,
        "lng": 80.031
    },
    timeout=240,
)
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": "cersai",
    "district_name": "Kancheepuram",
    "survey_number": "65",
    "sub_division": "4B",
    "lat": 12.8421,
    "lng": 80.031
  }),
});
const body = await res.json();
console.log(body.status, body.credits_charged, body.data);

Check CERSAI for any mortgage or charge on survey 65/4B in Kavanoor, Kancheepuram district.

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

• The registry files by the parent survey. A charge listed for survey 65 may sit on a neighbouring sub-division; read matching_assets before treating it as a charge on 65/4B.
• No match is not a clean bill. The registry matches the asset description a lender typed, and a mortgage described differently simply does not come back. Run the EC as well.
• The registry needs a city and a PIN code. Send lat and lng and they are worked out for you.
• Tamil Nadu property only. The search is sent to the registry for Tamil Nadu.
• The asset search does not take a name, so owner_name narrows nothing. To search by the borrower (PAN, CKYC, CIN or name), use the CERSAI borrower search.

Pricing

Questions

Related APIs