AAI NOC Register API: height clearances issued near a plot

Example

Request

curl -X POST https://verified.realestate/api/v1/tools/airport_noc_issued \
  -H "Authorization: Bearer $LANDLENS_KEY" \
  -H "Content-Type: application/json" \
  -d '{"lat":12.9675,"lng":80.15}'

Responsereal answer

{
  "ok": true,
  "status": "ok",
  "data": {
    "found": true,
    "mode": "point",
    "total": 114,
    "shown": 8,
    "radius_m": 1500,
    "clearances": [
      {
        "nocid": "CHEN/SOUTH/B/112817/264008",
        "structure": "Building",
        "where": "Pammal, Chennai",
        "aerodrome": "Chennai",
        "issued_on": "07 Dec 2017",
        "valid_up_to": "06 Dec 2025",
        "expired": true,
        "certificate_url": "https://nocs.verified.realestate/tn/Chennai/CHEN_SOUTH_B_112817_264008.pdf",
        "metres_from_point": 1324,
        "permissible_top_m_amsl": 24.38,
        "ground_level_declared_m_amsl": 13.25,
        "height_above_declared_ground_m": 11.13
      }
    ],
    "caveat": "Each of these was granted to that applicant, for those exact coordinates, on the ground level that applicant declared. It is evidence of what the Authority has allowed nearby, not permission for another plot, and only the Authority can issue one.",
    "source": "The Airports Authority of India's register of issued height clearances"
  },
  "credits_charged": 0
}

A real answer from the API for a point in Pallavaram, near Chennai airport, trimmed to one of the eight clearances, with the applicant's name left out.

What it returns

One call returns up to eight clearances. total says how many matched.

Field	What it holds
`mode, total, shown, radius_m`	How the search ran (point or filter), how many matched, how many came back, and the radius for a point.
`clearances[].nocid, structure, applicant, where, survey_numbers, aerodrome`	The certificate number, the kind of structure, who it was issued to, where, and the aerodrome.
`clearances[].issued_on, valid_up_to, expired`	When it was issued and whether its validity has run out.
`clearances[].permissible_top_m_amsl, ground_level_declared_m_amsl, height_above_declared_ground_m`	The top elevation allowed, the ground level the applicant declared and the height between them.
`clearances[].structures_on_this_certificate, nearest_structure`	For a certificate covering several structures: the count, the ranges, and the structure nearest your point.
`clearances[].metres_from_point`	How far the clearance is from the point you sent.
`clearances[].certificate_url`	The certificate itself.
`clearances[].marked_restricted, no_height_above_existing_ground`	Flags the certificate prints, with what they mean.
`caveat`	A neighbour's clearance is evidence of what was allowed nearby, not permission for another plot.

Inputs

The JSON body of the POST is the arguments. Send a point, or a survey number with its village, or a name, or a NOC ID. A point with filters narrows the filters to 1.5 km around it.

Argument	Type	What to send
`lat`	number	Latitude, from the parcel lookup. Finds clearances within 1.5 km.
`lng`	number	Longitude, from the parcel lookup.
`survey`	string	A survey or T.S. number, e.g. 44/2. Several may be separated by commas.
`village`	string	The village, strongly recommended with a survey number.
`district`	string
`airport`	string	The aerodrome, e.g. Chennai, Coimbatore, Tuticorin.
`name`	string	An owner or applicant name.
`nocid`	string	A certificate number, to confirm a document someone has produced.

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/airport_noc_issued \
  -H "Authorization: Bearer $LANDLENS_KEY" \
  -H "Content-Type: application/json" \
  -d '{"lat":12.9675,"lng":80.15}'

import os, requests

r = requests.post(
    "https://verified.realestate/api/v1/tools/airport_noc_issued",
    headers={"Authorization": f"Bearer {os.environ['LANDLENS_KEY']}"},
    json={
        "lat": 12.9675,
        "lng": 80.15
    },
    timeout=20,
)
body = r.json()
print(body["status"], body["credits_charged"], body["data"])

const res = await fetch("https://verified.realestate/api/v1/tools/airport_noc_issued", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.LANDLENS_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "lat": 12.9675,
    "lng": 80.15
  }),
});
const body = await res.json();
console.log(body.status, body.credits_charged, body.data);

What building heights has the Airports Authority cleared within 1.5 km of 12.9675, 80.1500? Show me the certificates.

Your AI searches the clearance register and links each certificate. It is free.

Responses

Every answer has the same envelope. What status can say for this call:

status	What it means
`ok`	One or more clearances matched.
`not_found`	Nothing matched, nothing to search by was sent, or the point is outside Tamil Nadu. Nothing is charged. It does not mean no height limit applies.
`free_limit_reached`	The account has used its free calls for the hour or the day. retry_after says how many seconds to wait; paid calls keep working.

Where the data comes from

Register

The Airports Authority of India's published register of height clearances (NOCs), with the certificates, for the aerodromes at Chennai, Coimbatore, Madurai, Tiruchirapalli, Tuticorin, Salem, Hosur, Vellore, Neyveli, Kayathar, Pondicherry and Tirupati.

Coverage

About 8,800 clearances issued from January 2016 to October 2026. The Authority publishes nothing issued before 1 January 2016.

How current

The register is read again and the certificates mirrored about once a quarter, so a clearance from the last few weeks may be missing.

How we read it

Searched in our copy of the register. A point search returns clearances within 1.5 km; survey numbers are matched against those printed on the certificate. Certificates are served from our own file host, because the Authority's portal does not open them by direct link.

Who uses it

Architects

See the heights the Authority actually cleared for neighbouring plots before applying for your own.

Lenders and advocates

Confirm a NOC ID in a builder's file against the Authority's register and open the certificate.

Due diligence teams

List the clearances issued to a builder or institution across aerodromes.

Limits and good practice

A clearance belongs to its own coordinates and declared ground level. It is not permission for another plot.
The register starts on 1 January 2016. Older clearances cannot be searched.
Nothing found is common away from approach paths and is not the same as no limit. For the zoning map limit use airport_height.
"(Restricted)" on a certificate is the Authority's word and is not defined by it; read the certificate.

Pricing

Free

The NOC register search costs nothing. Free calls have their own allowance per hour and per day, counted across every key and connected app on the account. Credits come from the same LandLens wallet as the chat and the minis. How billing works.

Calling at volume?

Free calls have an hourly and daily allowance. For more than that, or a platform built on these registers, we set up limits and a plan to match.

WhatsApp 99961 29996