Bulk Patta API: queue up to 200 land records at once
Yes. queue_land_records takes a list of up to 200 Tamil Nadu survey numbers and queues a land record fetch for each (patta, chitta, A-register or TSLR), to run in the background instead of one call at a time. It is the batch form of fetch_land_record, for a portfolio sweep, a collateral audit or a land bank. A batch of up to eight records costs 6 credits; each record beyond eight costs the same as one fetch_land_record call. A record the government register fails to return has its share refunded.
https://verified.realestate/api/v1/tools/queue_land_records- Price
- 6 credits when it starts, refunded if it fails
- Source
- Revenue department land registers
- Coverage
- Village and town survey land
- Answers in
- Queued at once; records arrive over minutes
What it returns
The call returns at once with what was queued. The records themselves are fetched in the background.
| Field | What it holds |
|---|---|
queued | How many records were queued. |
not_queued | How many were left out because the list was longer than 200. Never silent: queue the rest as a second batch. |
batch_price | The credits charged for the whole batch. |
surveys | The survey numbers queued, e.g. 65/4B. |
jobs[] | One entry per queued record: survey, job_id (for job_status) and status_url, a link that shows where that record stands and, once it is in, the record itself. |
Inputs
The JSON body of the POST is the arguments. One list, one entry per record.
| Argument | Type | What to send |
|---|---|---|
recordsrequired |
array | A list of up to 200 entries, each with district_code, taluk_code, village_code and survey_number, and optionally record_type, sub_division and patta_number, exactly as fetch_land_record takes them. |
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/queue_land_records \
-H "Authorization: Bearer $LANDLENS_KEY" \
-H "Content-Type: application/json" \
-d '{}'
import os, requests
r = requests.post(
"https://verified.realestate/api/v1/tools/queue_land_records",
headers={"Authorization": f"Bearer {os.environ['LANDLENS_KEY']}"},
json={},
timeout=60,
)
body = r.json()
print(body["status"], body["credits_charged"], body["data"])
const res = await fetch("https://verified.realestate/api/v1/tools/queue_land_records", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.LANDLENS_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({}),
});
const body = await res.json();
console.log(body.status, body.credits_charged, body.data);
Pull the patta for these survey numbers in Kavanoor village, Kundrathur taluk: 65/4B, 66/1, 66/2, 67/3A, 68.
Your AI queues them as one batch, says the price, and reports each record as it arrives.
Responses
Every answer has the same envelope. What status can say for this call:
| status | What it means |
|---|---|
ok | The batch was queued. Charged the batch price. |
not_found | No entry in the list had the codes and survey number a record needs. Nothing is charged. |
invalid_args | records is missing. |
insufficient_credits | The balance does not cover the batch price. |
Where the data comes from
The same registers fetch_land_record reads: the Tamil Nadu revenue department's patta and chitta, the A-register, and the Town Survey Land Register (TSLR).
Every revenue village and town in Tamil Nadu that the department has put online.
Live. Each queued record is read from the register when its turn comes.
Each entry is fetched exactly as fetch_land_record would fetch it. Entries missing a district code, village code or survey number are left out of the batch and out of the price.
Who uses it
Banks and NBFCs
Re-read the patta of every survey in a collateral book in one batch during an NPA or portfolio audit.
Developers
Check the recorded holders across a land bank before an acquisition closes.
Limits and good practice
- At most 200 records a call. A longer list is cut at 200 and not_queued says how many were left out.
- This call queues the work and returns. Follow each record by its job_id with job_status, or open its status_url, which needs no key and lasts 30 days.
- Each record has the same limits as fetch_land_record: a chitta needs a patta number, and a town survey needs its ward and block.
Pricing
Up to eight records cost 6 credits as one batch; each record beyond eight costs the same as one fetch_land_record call. A record the register fails to return has its share refunded. 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 a bulk API for Tamil Nadu patta records?
Yes, this one. One call queues up to 200 patta, chitta, A-register or TSLR fetches.
How much does a batch cost?
Up to eight records cost 6 credits together. Beyond eight, each record costs the same as one fetch_land_record call, so a long batch never costs more than fetching the records one by one.
What happens to a record the government register does not return?
Its share of the batch price is refunded.
How do I get each record back?
Every entry in jobs carries a job_id and a status_url. Poll job_status with the job_id, or open the status_url in a browser or a script; it shows queued or running until the record is delivered, then the record.
Should I use this or fetch_land_record?
For one or two records, fetch_land_record answers in the same call. For a list, queue it here in one call rather than looping.
Updated 22 Oct 2026 · OpenAPI description