---
title: "Who owns the plots next door"
method: POST
path: "/api/v1/tools/neighbours"
---

# Who owns the plots next door

`POST /api/v1/tools/neighbours`

## Request

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

The parcels SHARING A BOUNDARY with the parcel at a latitude/longitude, each with its recorded owner (both scripts) and a government/poramboke/road flag, in one response. Use for "who are my neighbours", "owners of adjacent plots", and road-access questions ("does my land touch a road / is it landlocked") - an adjacent parcel classified as road/street or government land IS the access evidence. Falls back to a nearby-parcels list when the pin is not inside any parcel. Costs 2 credits per call, waived when nothing is found.

## Request body

- object
  - `lat` number, required: Latitude in decimal degrees
  - `lng` number, required: Longitude in decimal degrees
  - `radius` number: Candidate search window in metres (10-500, default 150). Only used to gather candidates; adjacency itself is boundary-sharing.
  - `survey_number` string: When the plot is ALREADY RESOLVED to a survey number, pass it (without the sub-division) so the source parcel is anchored to that exact parcel. Without it the parcel is picked by point alone, and a centroid near a boundary can anchor to the NEIGHBOUR instead.
  - `sub_division` string: Sub-division of the resolved plot, e.g. "114" for 1017/114
  - `village_code` string: Village code of the resolved plot, when known

## 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)
