Registration Pulse (Intelligence)

What actually sold in a registered project, from the registered deeds: the registered deeds for the project's survey numbers are read, each sale deed matched to the filing's unit statement (flat and floor, flat number, or undivided share), and the page gives registered sales by month, first sales against resales, units still unsold against the filing, the price per square foot paid (low, median, high) and the ticket bands, with every deed listed. With rera_id: that project. With q: search the register for a project by name. Without either: the statewide figures and the projects most recently read. Answers "how many flats have registered in Sreerosh Aurelia", "what price per square foot are buyers paying there", "how fast is this project absorbing". Only projects whose deeds have been read carry deeds; a project not yet read says so with its unit statement status rather than showing zero sales. LandLens Intelligence, enterprise plan. Free of credits; the plan is the only requirement. Without it the call is refused (scope_denied, with the plan page) and nothing is charged.

post/api/v1/tools/intel_registrations

Request

  • Base URL: https://verified.realestate
  • URL: https://verified.realestate/api/v1/tools/intel_registrations
  • Auth: HTTP bearer

Request body

rera_idstring

The RERA registration number of the project to read.

qstring

Project or developer name to search the register for.

show'sales' | 'all'

sales (default): sale deeds only; all: every deed on the certificate, mortgages and releases included.

sort'date' | 'doc' | 'flat' | 'carpet' | 'consideration' | 'price' | 'kind' | 'confidence'

Deed table order; default date (newest first).

dir'asc' | 'desc'
limitinteger

Deeds, or search results, to return (default 25, at most 100).

Response

The envelope: ok, status, data, credits_charged, balance_after, request_id

Changes

No recorded changes to this operation across all 2 revisions of this API.