Every state keeps its land records differently. One API reads them the same way.
A land records API lets your software look up a plot, its published holders, government land rates and notices by code, not by captcha. IndiaPropertyRegister, built by Billion Insights, covers 19 crore+ plots across all 36 states and union territories at ₹0.40 per successful call, with ₹50 free credit.
A land records API is a programmatic interface that returns state revenue records (record of rights, plot maps, mutations), registration data and related notices as structured JSON, keyed by standard codes such as LGD village codes and ULPIN.
₹50 free credit on signup, no card and no approval. Revenue records are not proof of title, and nothing returned is a certified copy.
Last updated: 3 November 2026
Key takeaways
- One schema for 36 record systems. Khatauni, 7/12, RTC, jamabandi, patta and khatian all come back as the same plot object, with holders, mutations, deeds, charges, notices and government rates as arrays.
- Scale as of 3 November 2026: 6,83,627 villages with a page, 19,81,51,667 plots on the register (19 crore+) and 332 government sources tracked, per the coverage page.
- Simple pricing: ₹0.40 per successful call from a prepaid wallet. Errors and not-found lookups are free. A six-call property check costs ₹2.40.
- Real data in this guide: every JSON sample below is a trimmed response from a live call we made on 3 November 2026, with private holder names masked.
- It is evidence, not title. A revenue record shows who is recorded, not who owns. A lawyer’s title search is still the last word before you lend or buy.
What is a land records API, and why does India need one?
A land records API gives you machine-readable access to the record of rights, plot maps and related notices that India’s states publish on their own portals. India needs one because there is no single national land register: each state and union territory runs its own system, with its own record names, languages and search screens.
If you have ever pulled a khatauni from UP Bhulekh and then tried the same task on Maharashtra’s Mahabhulekh, you know the problem. Different hierarchies (janpad, tehsil, pargana, village in Uttar Pradesh; district, taluka, village in Maharashtra), different plot numbers (gata, khasra, survey number, dag), different scripts, and a captcha on almost every screen. For one property that is an afternoon. For a loan book, a proptech listing feed or a research project across a few thousand villages, it does not scale.
IndiaPropertyRegister (the site’s long name is India Property Register) reads those public sources on each state’s own schedule, stores what it reads with the date it read it, and serves it back through one REST API and one MCP server. It is built and operated by Billion Insights Ventures Pvt. Ltd., the Noida company behind eCourtsIndia and IndiaCos. If you are new to the family of APIs, our map of India’s public records APIs explains which one answers which question.
Plain words first: “record of rights” (RoR) is the state’s register of who holds a piece of land and on what terms. It is maintained for land revenue. Courts treat it as evidence of possession and revenue liability, not as a title deed. Every response from this API carries that note, and so should your product.
How does each state name its land records?
Each state uses its own name for the same idea. Uttar Pradesh calls the record of rights a khatauni, Maharashtra and Gujarat call it the 7/12, Karnataka calls it the RTC, and Punjab, Haryana and Rajasthan call it the jamabandi. The table below comes from the register’s land records guide, read on 3 November 2026.
| State or UT | Record of rights and related records | Online status (per the guide) |
|---|---|---|
| Uttar Pradesh | Khatauni, Khasra, Certified khatauni | Online |
| Maharashtra | 7/12 (Satbara), 8A, Property Card, K-Prat | Online |
| Gujarat | VF-7 (7/12), VF-8A, VF-6 (Hakk Patrak), 135-D notice | Online |
| Karnataka | RTC / Pahani, Mutation Register, Khatha extract, i-RTC | Online |
| Haryana | Jamabandi, Mutation (Intkal), Fard Badar, Khasra Girdawari | Online |
| Punjab | Jamabandi, Fard, Mutation (Intkal) | Online |
| Rajasthan | Jamabandi, Girdawari, Namantaran | Online |
| Bihar | Jamabandi register, Khatiyan, LPC | Online |
| Madhya Pradesh | Khasra, Khatauni, Aabadi Adhikar Abhilekh | Online |
| Tamil Nadu | Patta, Chitta, A-Register, FMB | Online |
| Telangana | Land status, Pattadar Passbook, Encumbrance statement | Online |
| Andhra Pradesh | 1B, Adangal / Pahani, FMB / LP map, e-Passbook | Online |
| West Bengal | Khatian, Plot (Dag), Porcha | Online |
| Odisha | RoR (Khatian) | Online |
| Kerala | Thandaper / Basic Tax Receipt, ReLIS land information | Online |
| Delhi | Jamabandi and Khatouni, registered deed e-Search, UPIC record | Partly online |
| Nagaland | Record of Rights | No online records |
The API exposes the same knowledge as data. Call /sources?state=9 for Uttar Pradesh and you get the record names in English and Hindi, the hierarchy (“District (Janpad), Tehsil, Pargana, Village, Gata / Khasra”) and a short glossary: bandhak is the mortgage line in the khatauni, abhyukti is the remarks column and vad-grast marks a disputed plot. That glossary matters more than it looks. A credit analyst in Mumbai reading a Jewar khatauni needs to know that a remark saying “बंधक मुक्त” means a mortgage was released.
What does IndiaPropertyRegister cover today?
As of 3 November 2026 the register holds 19,81,51,667 plots across 6,83,627 villages in all 36 states and union territories, drawn from 332 tracked government sources. The record of rights itself is loaded for 27 states and UTs; for 7 more the register knows the state portal but has not loaded the records yet, and for Meghalaya and Nagaland it knows of no online source.
| Measure | Figure | Where we read it |
|---|---|---|
| States and union territories | 36 | /api/v1/stats, 3 Nov 2026 |
| Districts / tehsils | 783 / 6,360 | /api/v1/stats |
| Villages with LGD codes and a page | 6,83,627 | /stats and /coverage page |
| Plots (parcels) on the register | 19,81,51,667 (19 crore+) | /stats (data date 19 Oct 2026) |
| Urban local bodies / wards | 5,222 / 63,924 | /api/v1/stats |
| Government sources tracked | 332 | /coverage and /sources pages |
| Published holder records | 44 crore+ | /api page |
| City properties from municipal tax records | 3.8 crore+ in 1,233 cities | /api page |
| Bank and tribunal auction listings | 1,23,412 (610 upcoming) | /auctions page |
Coverage is uneven by layer, and the API says so. The /coverage endpoint returned 245 state-by-layer rows on 3 November 2026, across ten layers: holders, mutations, plots, circle rates, deeds, acquisition notices, notified land, national programmes, RERA and property tax. Each row has a status and a last_run date. For Uttar Pradesh, for example, the circle-rate layer held 8,86,232 records last run on 13 October 2026, land-acquisition notices held 1,831 records last run on 2 November 2026, and notified land held 3,988 records last run on 12 October 2026. Check this endpoint before you promise a customer coverage in a particular state.
What are LGD codes and ULPIN, and why do they matter?
An LGD code is the government’s numeric code for a state, district, tehsil or village in the Local Government Directory kept by the Ministry of Panchayati Raj; ULPIN is the 14-digit unique land parcel identification number, also called Bhu-Aadhaar. Together they let you point at a place and a plot without depending on spellings.
Names break joins. A search for “Achheja” on 3 November 2026 returned Achheja in Gautam Buddha Nagar, but also Achher in Doda, Achhej in Jhajjar, Achheta in Chhota Udaipur and Achhaija in Hapur. The LGD code removes that doubt: Achheja in Dadri tehsil is village 120128, in tehsil 742, in district 144, in state 9. Every village endpoint in the API takes that integer.
ULPIN goes one level deeper, to the parcel. The Department of Land Resources concept note describes it as a 14-digit ID generated from the geo-referenced coordinates of a parcel’s vertices, so that one plot keeps one identity across departments. Adoption varies. The register’s Uttar Pradesh page shows ULPIN assigned for 93.9% of plots, and its Gautam Buddha Nagar district page shows 97.6% of plots with ULPIN (DILRMP figures as of 12 October 2026). Yet the plot record we pulled in Achheja returned "ulpin": null. Null means the register has not read one for that plot. It does not mean the plot has none.
Which endpoints does the land records API have?
The API has 30 data endpoints under one base URL, https://indiapropertyregister.com/api/v1, plus free account endpoints. The full list, with parameters, is in the public OpenAPI 3.1 spec and the API docs. These are the ones most teams use first.
| Job | Endpoint | What it returns |
|---|---|---|
| Find a place | GET /search?q= | States, districts, tehsils and villages by name, or the villages in a 6-digit pincode |
| Read a village | GET /village/{lgd} | Codes, hierarchy, pincode, area, neighbours, land-record sources, plot count |
| Find a plot | GET /village/{lgd}/plots?plot= | Matches for a plot number such as 123/2A, each with an ipr_id |
| Read a plot | GET /plot/{ipr_id} | Holders as published, mutations, deeds, charges, tax, court cases, notices, restricted land, government rates |
| Search holders | GET /owners/search?name= | Plots by published holder name, optionally by state or district |
| Government rates | GET /village/{lgd}/rates | Circle rate, guideline value, jantri, ready reckoner or DLC rows with year and source |
| Restricted land | GET /village/{lgd}/layers | Restricted and notified land, land acquisition notices, programme progress |
| City property tax | GET /cities, /city/{code}/properties | Municipal tax records, 200 properties a page |
| Auctions | GET /auctions | Bank and tribunal property auctions, newest first, 50 a page |
| RERA | GET /rera/projects | RERA projects by state, district or pincode, with units and dates |
| Deeds | GET /deeds/offices, /deeds | Sub-registrar offices and registered deeds, 100 a page |
| Ask in words | GET /ask?q= | A question in English or Hindi, parsed, answered only from matching records, with URLs |
Authentication is a key in Authorization: Bearer or X-API-Key. Errors come back as JSON with error, message and docs fields: 401 api_key_required, 402 insufficient_balance, 404 not_found, 429 quota_exceeded and 503 when an upstream service times out. We tested the no-key case on 3 November 2026 and got the 401 with a sign-up link in the message.
Worked example: one village in Gautam Buddha Nagar, call by call
Here is the exact chain we ran on 3 November 2026 for a village in Dadri tehsil, Gautam Buddha Nagar, the district where Billion Insights has its registered office. Four calls, ₹1.60, and you go from a village name to a plot record.
export IPR_KEY="your_key_here" # keep it in an env var, never in code
BASE=https://indiapropertyregister.com/api/v1
# 1. Find the village by name
curl -s -H "Authorization: Bearer $IPR_KEY" "$BASE/search?q=Achheja"
# 2. Read the village by its LGD code
curl -s -H "Authorization: Bearer $IPR_KEY" "$BASE/village/120128"
# 3. Find a plot by its gata (plot) number in that village
curl -s -H "Authorization: Bearer $IPR_KEY" "$BASE/village/120128/plots?plot=$GATA_NO"
# 4. Read the full plot record
curl -s -H "Authorization: Bearer $IPR_KEY" "$BASE/plot/$IPR_ID" # the ipr_id returned by step 3The village call (step 2) returned this, trimmed to the useful fields. The neighbours array listed seven villages; we show one.
{
"lgd": 120128,
"name": "Achheja",
"census2011": "120128",
"pincode": "203207",
"area_hectares": 419.29,
"state": {"lgd": 9, "name": "Uttar Pradesh"},
"district": {"lgd": 144, "name": "Gautam Buddha Nagar"},
"tehsil": {"lgd": 742, "name": "Dadri"},
"block": {"lgd": 1125, "name": "Bisrakh"},
"plots": 1479,
"neighbours": [{"lgd": 120127, "name": "Bisnoli", "tehsil": "Dadri"}],
"land_record_sources": [
{"id": "up_bhulekh_ror", "layer": "ror", "name": "UP Bhulekh",
"records": ["Khatauni", "Khasra"], "on_register": true},
{"id": "up_igrs", "layer": "registration", "name": "IGRS UP (PRERNA)",
"records": ["Registered deed", "Encumbrance (Bharmukt) certificate"],
"on_register": false}
],
"note": "Revenue records are not proof of title and this is not a certified copy. Verify with the issuing office."
}Two things to notice. First, land_record_sources tells you honestly what is loaded: the khatauni is on the register, while registered deeds and the Bharmukt (encumbrance) certificate from IGRS UP are not, so for those you still go to the sub-registrar. Second, the village has 1,479 plots on the register, which matches the count on the public village page.
The plot call (step 4) returned the record below. It lists five recorded holders; we show one, masked the way the public page masks it. We have also withheld the plot number and the ipr_id, so that no reader can look up a private family’s land from this page.
{
"ipr_id": "(withheld)",
"plot_no": "(withheld)",
"record_system": "up_khasra",
"ulpin": null,
"area_sqm": null,
"land_class": "1-क",
"tenure": "भूमि जो संक्रमणीय भूमिधरों केअधिकार में हो।",
"village": {"lgd": 120128, "name": "Achheja"},
"tehsil": {"lgd": 742, "name": "Dadri"},
"holders": [
{"name": "न***", "relation": "प***", "share": null, "right": "owner",
"since": "2026-11-01", "read_on": "2026-10-31"}
],
"mutations": [], "deeds": [], "charges": [], "court_cases": [],
"notices": [], "restricted_land": [], "government_rates": [],
"first_seen": "2026-11-01",
"last_read": "2026-11-01",
"note": "Revenue records are not proof of title and this is not a certified copy. Verify with the issuing office."
}Read it slowly. Land class 1-क with the tenure line “land held by transferable bhumidhars” is the common agricultural tenure in Uttar Pradesh. The since date of 1 November 2026 is the day the register first loaded the entry, not the day the holders acquired the land. Empty arrays mean “nothing read”, not “nothing exists”: this village’s deeds are not on the register yet, so deeds: [] tells you nothing about sales. That is exactly the discipline we ask readers of court data to follow, and it applies here too.
Government rates are a separate call. For Rohi, a village in Jewar tehsil of the same district (LGD 120385), the rates endpoint returned four rows from the UP circle rate list for 2023, read by the register on 13 October 2026: commercial ₹30,000 per sq m, construction cost ₹15,000 per sq m, and two non-agricultural land rates of ₹2,800 and ₹3,500 per sq m. The same question asked in plain English through /ask?q=circle rate in Rohi, Gautam Buddha Nagar returned the same four figures with links back to the village page. The API adds a useful line to every rates response: “The rate is a floor set by the state, not a market price.”
import os
import requests
BASE = "https://indiapropertyregister.com/api/v1"
HEADERS = {"Authorization": f"Bearer {os.environ['IPR_KEY']}"}
def get(path, **params):
r = requests.get(BASE + path, headers=HEADERS, params=params, timeout=30)
if r.status_code == 402:
raise RuntimeError("Wallet empty: top up from your account page")
if r.status_code == 429:
raise RuntimeError("Daily cap reached; it resets at midnight IST")
r.raise_for_status()
return r.json()
rates = get("/village/120385/rates") # Rohi, Jewar tehsil
for row in rates["rates"]:
print(row["land_use"], row["rate_inr"], "per", row["per"], row["year"])
# Output on 3 November 2026:
# Commercial 30000 per sqm 2023
# Construction cost 15000 per sqm 2023
# Non-agricultural land 2800 per sqm 2023
# Non-agricultural land 3500 per sqm 2023
What else can you query: city property tax, auctions, RERA and deeds?
Rural plots are only half of Indian property. The same key reads municipal tax records, bank auctions, RERA projects and, where loaded, registered deeds.
- City property tax.
/cities?state=9returned 193 Uttar Pradesh towns and cities with tax records on 3 November 2026. Lucknow Municipal Corporation alone showed 7,54,648 properties in 114 areas. Use/city/{code}/propertiesto page through an area, 200 at a time. - Auctions.
/auctions?district=144listed liquidation and bank auctions in Gautam Buddha Nagar, newest first. The top entry was an IBBI liquidation sale of Fantastic Buildcon Pvt Ltd with a reserve price of ₹65,19,56,145 (about ₹65.2 crore), an earnest money deposit of ₹6,51,95,614 and an auction date of 17 November 2026. Bank e-auctions of flats and plots followed. Our borrower due diligence guide follows that liquidation case across company and court records. - RERA.
/rera/projects?district=144returned the newest UP RERA registrations first. One example: DXN-ORION by Emerald Promoters Pvt. Ltd., 861 units, registered on 8 October 2026 with a completion date of 5 January 2031. - Deeds. Deed coverage is still thin and you should check before you build on it.
/deeds/offices?state=27returned six Maharashtra sub-registrar offices on 3 November 2026, the largest with 95 deeds between 2021 and 2026.
Court cases sit in the plot record as a court_cases array where a state links them to the plot. For a full litigation search on a holder or a developer, use the eCourtsIndia API, which indexes 35 crore+ case records. For land disputes heard by tehsildars, SDMs and boards of revenue, read our guide to India’s revenue boards, because many of those matters never reach a civil court.
How much does the land records API cost?
The land records API costs ₹0.40 per successful call (HTTP 200), paid from a prepaid wallet. New accounts get ₹50 of free credit, which is 125 calls, with no card and no approval. Errors, not-found lookups, refused calls and account endpoints are free. Searches that return no rows are billed, because the search itself ran.
| Item | Price | What you get |
|---|---|---|
| Successful call | ₹0.40 | One HTTP 200 response; each page of a list is one call |
| Free credit on signup | ₹50 | 125 calls |
| Top-up ₹500 | ₹590 with 18% GST | 1,250 calls |
| Top-up ₹5,000 | ₹5,900 with 18% GST | 12,500 calls |
| Top-up ₹50,000 | ₹59,000 with 18% GST | 1,25,000 calls |
| Daily safety cap | 100,000 calls per key | 429 quota_exceeded after that; resets at midnight IST |
| Enterprise | Custom | Scheduled feeds and higher caps; no bulk download on self-serve |
Some quick sums. A six-call property check (search, village, plot lookup, plot, rates, layers) is ₹2.40. One thousand such checks a month is ₹2,400. A portfolio job that makes 1 lakh calls a month is ₹40,000 before GST. If you already use the IndiaCos API for GST and company checks, the price per call is the same, so budgeting across both is simple.
Can you use it from Claude, ChatGPT or Cursor?
Yes. IndiaPropertyRegister runs a remote MCP server at https://indiapropertyregister.com/mcp that works with Claude, ChatGPT, Cursor and any MCP client. You sign in with OAuth 2.1, so there is no key to paste, and calls bill to the same wallet as the API.
In Claude Code the one-line setup published in the site’s llms.txt is claude mcp add --transport http indiapropertyregister https://indiapropertyregister.com/mcp. The server exposes 29 tools, including find_plot, get_plot, search_owner, get_village_rates, get_village_layers, list_auctions, list_rera_projects and ask. For agents there is more: a public llms.txt, the OpenAPI spec, an MCP server card under /.well-known/, and any page served as Markdown when you send Accept: text/markdown. The idea is the same one we wrote about for courts in llms.txt for Indian courts.
Our MCP guide for court, company and land data sets up all three Billion Insights servers side by side. If you only want courts for now, connect the eCourtsIndia MCP to Claude first.
How does it compare with other land record APIs in India?
Disclosure first: Billion Insights makes IndiaPropertyRegister, so read this section as a fair map, not a neutral review. We quote each provider only from its own page, read on 3 November 2026, and we make no claim about anyone’s accuracy.
| Provider | What its page says it offers | Published price? | When to choose it instead |
|---|---|---|---|
| Landeed document procurement API | “28 states live”; ECs, certified deed copies, RTC, 7/12, patta, khatauni, mutation entries, CERSAI and ROC charge searches; same-day where the record is digital | Not published on the page; access by request, no self-serve key | You need certified copies or counter-collected documents procured for you |
| Meon Gujarat land record check API | Gujarat checks by survey number, district, taluka or landowner details; owner name, land type, area, mutation status | Not published on the page | You only need Gujarat and already use Meon for KYC |
| Surepass land record check APIs | Gujarat ownership and boundary by district, taluka, village and block; the site also lists a general Land Record Check API | Not published on the page | Your KYC stack is already on Surepass |
| parse.bot Mahabhulekh listing | Third-party wrapper over Maharashtra Bhulekh: 7/12, 8A and property card by ID, HTML in Marathi; no owner-name search, no ferfar or EC | Yes: Free 100 credits, Hobby $30 for 1,000, Developer $100 for 5,000 a month | A small Maharashtra-only hobby or prototype |
| State portals such as UP Bhulekh and Mahabhulekh | The official record, free to view, with paid certified copies | Free to view; certified copies at state fees | Always, before a transaction, for the certified copy |
| Square Yards via RBIH’s Unified Lending Interface | Reported on 8 April 2026: over 100 million property registration records digitised; e-Valuation and Title Search through ULI in eight states | Not published | You are a regulated lender already integrated with ULI |
Where IndiaPropertyRegister is different: it is self-serve with a published per-call price, it covers all 36 states and UTs in one schema, it publishes its OpenAPI spec and MCP server openly, and it puts rural plots, city tax records, rates, notices, auctions and RERA behind one key. Where others are stronger: document procurement and certified copies (Landeed), and integration with ULI for lenders inside that network (Square Yards). Many teams will use more than one.
What a land records API does not tell you
A land records API tells you what a government record says on the day it was read. It does not tell you who owns the land. Keep these limits in front of every user.
- Not proof of title. A khatauni, 7/12 or jamabandi records possession and revenue liability. Title flows from registered documents, inheritance and court decrees.
- Not a certified copy. Nothing the API returns is certified. Banks, courts and registrars want certified or digitally signed copies from the issuing office.
- Mutation lag. The public plot page warns that holder names “can lag behind mutations and court orders”. A sale registered last month may not show in the record of rights yet.
- Empty is not clear. An empty
chargesorcourt_casesarray means nothing was read for that plot. It is not a no-encumbrance certificate. For charges, CERSAI is the official registry. - A name is not a person.
/owners/searchmatches published names. Different people share names, and the response says so. Our study of same-name false matches in court records applies here too. - Rates are floors. Circle rates set the minimum value for stamp duty. They are not market prices or valuations.
- Map overlays are approximate. Restricted-land checks overlay forest, CRZ, eco-sensitive zone and industrial estate maps on village boundaries. A small overlap share needs a surveyor, not a conclusion.
What still needs a lawyer: a title search report that traces the chain of documents (commonly over 30 years), certified copies of the record of rights and mutation orders, an encumbrance certificate from the sub-registrar, a CERSAI search, a court and revenue-court search on every holder, and a site inspection. Our property collateral checklist for lenders lays that out step by step, and the family property dispute index shows how often inheritance disputes sit behind clean-looking records.
Who uses a land records API?
Lenders and NBFCs use it to pre-screen collateral before the legal team spends a day on a file. Proptech platforms use it to show buyers the government rate, the RERA record and nearby auctions on a listing. Law firms use it to prepare a title search faster, then verify everything against certified copies. Agritech companies use it to confirm a farmer is a recorded holder before a crop loan or insurance policy. Researchers and journalists use the village and acquisition layers to study land use and infrastructure projects. If your team already follows our legal due diligence workflow, land records slot in as the property step.
The data licence is plain. Your own business use, commercial included, and showing individual records to your users are allowed. Resale, redistribution, building a competing database, bulk scraping and AI training need written permission from support@indiapropertyregister.com. Cite records as the site suggests: India Property Register, page title, URL, accessed date.
Sources and method
- IndiaPropertyRegister coverage page, land records guide, sources page, auctions page and API page, read 3 November 2026.
- IndiaPropertyRegister API docs, OpenAPI spec, llms.txt and auth.md, read 3 November 2026.
- Live API calls on 3 November 2026: /stats, /coverage, /search, /village/120128, /village/120128/plots, /plot/{ipr_id} (plot identifiers withheld), /village/120385/rates, /ask, /sources?state=9, /cities?state=9, /auctions?district=144, /rera/projects?district=144, /deeds/offices?state=27. Responses trimmed; private names masked.
- Uttar Pradesh state page and Gautam Buddha Nagar district page on indiapropertyregister.com (DILRMP and SVAMITVA figures as of 12 October 2026), read 3 November 2026.
- Ministry of Panchayati Raj, Local Government Directory (LGD), read 3 November 2026.
- Department of Land Resources, ULPIN (Bhu-Aadhar) concept note, read 3 November 2026.
- Provider pages quoted in the comparison table (Landeed, Meon, Surepass, parse.bot), each read 3 November 2026; Square Yards and RBIH report on GeoSquare, dated 8 April 2026, read 3 November 2026.
Frequently asked questions
Is there an API for land records in India?
Yes. There is no official national land records API, but IndiaPropertyRegister offers one REST API and MCP server over the public records of all 36 states and UTs. It returns plots, published holders, mutations, government rates, notices, auctions and RERA projects as JSON at ₹0.40 per successful call. See the API docs for every endpoint.
How much does the IndiaPropertyRegister API cost?
Each successful call costs ₹0.40 from a prepaid wallet, and errors or not-found lookups are free. New accounts get ₹50 of free credit, about 125 calls, without a card. Top-ups are ₹500, ₹5,000 or ₹50,000 plus 18% GST. There is no subscription. Details are on the API page.
Can I get a khatauni or 7/12 extract through an API?
You can read the record-of-rights data behind a khatauni, 7/12, RTC or jamabandi as structured JSON wherever the state’s records are on the register. You cannot get a certified copy through the API. For that, use the state portal or tehsil office. The land records guide lists each state’s record names.
Does a land records API prove who owns a property?
No. A record of rights shows who is recorded as holding land for revenue purposes, on the date it was read. Ownership depends on registered documents, inheritance and court orders, so a lawyer’s title search is still needed. Our collateral check guide explains what to add.
What is an LGD code for a village?
An LGD code is the numeric code the Local Government Directory gives each state, district, tehsil and village. It avoids spelling clashes between villages with similar names. Achheja in Dadri tehsil, Gautam Buddha Nagar, for example, is LGD 120128. Every village endpoint takes this code; find it with the states directory.
Can I check circle rates through the API?
Yes. The /village/{lgd}/rates endpoint returns each state’s published government rate, whether called a circle rate, guideline value, jantri, ready reckoner or DLC rate, with the land use, unit, year and date read. Remember that it is a floor for stamp duty, not a market value. Coverage by state is on the coverage page.
Can I use IndiaPropertyRegister inside Claude or ChatGPT?
Yes. Add the remote MCP server at indiapropertyregister.com/mcp to Claude, ChatGPT, Cursor or another MCP client and sign in with OAuth. Calls bill to the same wallet as the API. Our MCP guide shows the setup for all three Billion Insights servers.
Important: IndiaPropertyRegister is a private service built from public government records on a best-effort basis and is not affiliated with any government department. Revenue and tax records are not proof of title, and nothing returned is a certified copy. Holder names are shown as published; a name is not proof of identity. Figures in this post were read live on 3 November 2026 and will change. This is not legal advice. Billion Insights Ventures Pvt. Ltd. (CIN U62090UP2026PTC241369, Noida) holds ISO 9001:2015, ISO/IEC 20000-1:2018 and ISO/IEC 27001:2022 certification (9001, 20000-1, 27001). Found an error? Write to support@ecourtsindia.com.
Start with one village you know. Four calls will show you more about India’s land records than a week of portals.