---
title: "Resolve parcel"
method: POST
path: "/api/v1/tools/resolve_parcel"
---

# Resolve parcel

`POST /api/v1/tools/resolve_parcel`

## Request

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

Resolve a latitude/longitude to the Tamil Nadu land parcel: survey number, subdivision, village/taluk/district, rural vs urban, ULPIN, extent and boundary GeoJSON. Use it with a REAL coordinate only: a pin the user dropped or shared, a coordinate or map link the user typed, a parcel already held in this conversation, or a lat/lng an earlier tool returned (a place search or a survey-to-map lookup). Never estimate a coordinate for a place NAME: a bare village, town or locality name goes first to the place-name lookup (a revenue village or town) or the place search (a locality, landmark or address), and this runs on the point that returns. For an URBAN parcel the result also carries firka_ward_number and urban_block_number: pass them to the land record fetch as ward_code and block_code, because a town survey number is unique only within a block and the TSLR cannot be filed correctly without them. Free.

## Request body

- object
  - `lat` number, required: Latitude in decimal degrees, from the user, the map or an earlier tool result; never estimated
  - `lng` number, required: Longitude in decimal degrees, from the user, the map or an earlier tool result; never estimated

## 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/7923c1c24431?raw)