Temple Land API: is this survey HR&CE temple land?
Yes. temple_land checks a Tamil Nadu survey number against the Hindu Religious and Charitable Endowments (HR&CE) department's temple land register: whether it is recorded as temple land, which temple holds it, its patta number, extent and the A-register or TSLR reference. It can also list a temple's holdings by temple name, or count the temple land recorded in a village. The register holds about 214,000 temple land parcels. It costs 1 credit per check, including a check that comes back clear.
https://verified.realestate/api/v1/tools/temple_land- Price
- 1 credit per answer
- Source
- HR&CE temple land register
- Coverage
- About 214,000 parcels
- Answers in
- Usually under a second
Example
curl -X POST https://verified.realestate/api/v1/tools/temple_land \
-H "Authorization: Bearer $LANDLENS_KEY" \
-H "Content-Type: application/json" \
-d '{"district":"Chennai","village":"Triplicane (Part 2)","survey_number":"2322","block":"0040"}'
{
"ok": true,
"status": "ok",
"data": {
"found": true,
"is_temple_land": true,
"total_matches": 1,
"survey": "2322",
"parcels": [
{
"temple": "Kandaswamy Temple, Thiruporur, 603110",
"temple_id": 1734,
"village": "-",
"town": "Triplicane (Part 2)",
"block": "0040",
"taluk": "Mylapore",
"district": "Chennai",
"survey": "2322/-",
"old_survey": "-",
"patta_no": 0,
"extent": 203,
"register_ref": "1~LD/1734/340"
}
]
},
"credits_charged": 1
}
A real answer from the API (22 Oct 2026), with the reading note left out.
What it returns
A parcel check returns is_temple_land and the matching rows. A clear answer (is_temple_land false) is a real answer and is charged.
| Field | What it holds |
|---|---|
is_temple_land | true when the survey is recorded as temple land; false when the register has no row for it. |
parcels | Up to 10 matching rows: temple, temple_id, village or town, block, taluk, district, survey, old_survey, patta_no, extent (as the register writes it) and register_ref (the A-register or TSLR reference). |
total_matches | How many rows matched, when there are more than 10. |
survey | The survey you asked about, so your own sub-division can be told apart from its neighbours. |
temples | With temple_name: up to five temples matching the name, each with district, parcel_count and a sample of its parcels. |
message | On a clear answer: what it does and does not establish. |
Ways to call it
Check a survey, list a temple's land, or count a village's temple land.
Is this survey temple land?
resolve_parcel gives the district, village and survey for a map point.
{"district": "Chennai","village": "Triplicane (Part 2)","survey_number": "2322","block": "0040"}
A temple's land
Add a district to narrow a common name.
{"temple_name": "Kapaleeswarar","district": "Chennai"}
Inputs
The JSON body of the POST is the arguments. Send a temple_name, or a district with a village (and a survey number to check one parcel).
| Argument | Type | What to send |
|---|---|---|
district |
string | The revenue district name, e.g. Chennai. |
taluk |
string | |
village |
string | The village, or the town for town survey land, e.g. Triplicane (Part 2). |
survey_number |
string | |
sub_division |
string | |
block |
string | For a town survey number: its block, from the plot record. |
temple_name |
string | Search by temple instead of by parcel. |
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.
curl -X POST https://verified.realestate/api/v1/tools/temple_land \
-H "Authorization: Bearer $LANDLENS_KEY" \
-H "Content-Type: application/json" \
-d '{"district":"Chennai","village":"Triplicane (Part 2)","survey_number":"2322","block":"0040"}'
import os, requests
r = requests.post(
"https://verified.realestate/api/v1/tools/temple_land",
headers={"Authorization": f"Bearer {os.environ['LANDLENS_KEY']}"},
json={
"district": "Chennai",
"village": "Triplicane (Part 2)",
"survey_number": "2322",
"block": "0040"
},
timeout=30,
)
body = r.json()
print(body["status"], body["credits_charged"], body["data"])
const res = await fetch("https://verified.realestate/api/v1/tools/temple_land", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.LANDLENS_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
"district": "Chennai",
"village": "Triplicane (Part 2)",
"survey_number": "2322",
"block": "0040"
}),
});
const body = await res.json();
console.log(body.status, body.credits_charged, body.data);
Is town survey 2322, block 40, in Triplicane temple land? Which temple holds it?
Your AI says the price, checks the HR&CE register, and names the temple and its register reference.
Responses
Every answer has the same envelope. What status can say for this call:
| status | What it means |
|---|---|
ok | The check ran: is_temple_land is true or false, or the temple was found. Charged 1 credit. |
not_found | No temple matches the name you sent, or neither a temple_name nor a district or village was sent. Nothing is charged. |
Where the data comes from
The land register of the Tamil Nadu Hindu Religious and Charitable Endowments department: each temple's land holdings with the survey number, patta, extent and its A-register or TSLR reference, and the department's list of temples.
About 214,000 temple land parcels across Tamil Nadu, village and town survey land, in our copy of the department's land register. Not every temple's holdings are in it yet.
The temple list is refreshed every 90 days. The land holdings are refreshed by a supervised run about once a year, since the department's land report sits behind a mobile number and OTP.
Matched by district (every spelling the register files it under), village or town, and the old or new survey number. For town survey land, the block picks the row, since a town survey number repeats across blocks. The sub-division is not filtered on, so a neighbouring sub-division held by a temple shows too.
Who uses it
Buyers and brokers
Check a plot against the temple land register before an advance is paid. Temple land needs HR&CE consent to transfer.
Law firms
Cite the temple and its register reference in a title opinion, or list a temple's holdings in a dispute.
Lenders
Screen collateral for endowment land before sanction.
Limits and good practice
- A clear answer means the register has no row for the survey. It is a good sign, not a legal guarantee: not every temple's holdings are in the register yet.
- The sub-division is not filtered on. Read each row's survey against your own sub-division.
- A town survey number repeats across blocks. Send block, or the answer may include another block's parcel.
- Extent is given as the register writes it, without a unit.
Pricing
Each check costs 1 credit, whether it finds temple land or comes back clear; nothing when a temple name matches no temple. Credits come from the same LandLens wallet as the chat and the minis. How billing works.
For thousands of calls a month, a portfolio sweep or a platform built on these registers, we quote a customised bulk price, with invoicing to match.
Questions
Is there an API to check if land in Tamil Nadu is temple land?
Yes, this one. It checks a survey number against the HR&CE temple land register and names the temple that holds it.
How much does a temple land check cost?
1 credit per check, including a check that comes back clear.
Does a clear answer mean the land is not temple land?
It means the register has no row for that survey. That is a good sign but not a guarantee, since not every temple's holdings are in it yet. Read it with the patta and the EC.
Can I list all the land of one temple?
Yes. Send temple_name, with a district to narrow a common name. Each matching temple comes back with its parcel count and a sample of its parcels.
Updated 22 Oct 2026 · OpenAPI description