---
title: "Revenue court cases on a survey"
method: POST
path: "/api/v1/tools/court_cersai"
---

# Revenue court cases on a survey

`POST /api/v1/tools/court_cersai`

## Request

- Base URL: `https://verified.realestate`
- URL: `https://verified.realestate/api/v1/tools/court_cersai`
- Auth: HTTP bearer

Court case and CERSAI (mortgage / security interest) checks. subject picks the register: "revenue_court" = revenue court cases on a survey (needs the revenue codes, resolve them first from names, plus the survey number); "civil_court" = a civil court case by its CNR number; "cersai" = CERSAI registered charges / mortgages on a property (needs owner name or district, plus survey / plot / door number) - this is a slow paid search, so it returns an approval card the user must confirm before it runs; "ecourt" = all court cases across India by a person's name (paid vendor search, also returns an approval card). Never present a cersai or ecourt proposal as fetched data. Costs 2 credits per call, waived when nothing is found.

## Request body

- object
  - `subject` 'revenue_court' | 'civil_court' | 'cersai' | 'ecourt', required: Which check to run
  - `district_code` string: Revenue district code (revenue_court)
  - `taluk_code` string: Revenue taluk code (revenue_court)
  - `village_code` string: Revenue village code (revenue_court)
  - `survey_number` string: Survey number WITHOUT the sub-division, e.g. "1511" for parcel 1511/2 (revenue_court, cersai). Put the sub-division in sub_division, do not join them here.
  - `sub_division` string: Sub-division, if any, e.g. "2" for parcel 1511/2 (revenue_court, cersai)
  - `cnr_number` string: CNR number like TNCC01-001234-2024 (civil_court)
  - `owner_name` string: Person / owner name (cersai, ecourt)
  - `district_name` string: District NAME, e.g. Chennai (cersai)
  - `city` string: City / town / village (cersai: the portal requires it; if unknown, pass lat/lng instead and it is resolved automatically)
  - `pincode` string: 6 digit PIN code (cersai: the portal requires it; if unknown, pass lat/lng instead and it is resolved automatically - do NOT ask the user for a PIN code the map already knows)
  - `lat` number: Latitude of the parcel (cersai: used to auto-resolve the PIN code and city when they are not known)
  - `lng` number: Longitude of the parcel (cersai: used with lat)
  - `plot_no` string: Plot number (cersai, alternative to survey)
  - `door_no` string: Door number (cersai, alternative to survey)

## Response `200`

The envelope: ok, status, data, credits_charged, balance_after, request_id

## Other responses

- `401`: No valid credential
- `402`: Not enough credits
- `429`: Rate limit

---

[API](https://skmtc.dev/verified/apis/landlens-tool-api.md) · [All operations](https://skmtc.dev/verified/apis/landlens-tool-api/llms.txt) · [OpenAPI document](https://skmtc.dev/verified/apis/landlens-tool-api/revisions/54f851c86cc1?raw)