Subdivisions of a survey

List the SUBDIVISIONS recorded under a survey number (the register's own split list: 178/1A, 178/1B, 178/2 and so on) with a count. Use for "how many subdivisions does survey 178 have", "list the subdivisions of 178", "what are the sub divisions in this survey", "does 178/1C exist", "is 45/2 a valid subdivision", and BEFORE an ownership or document pull when the user gave a bare survey number, because neighbouring subdivisions can have different owners. Pass the revenue codes (from the free parcel lookup or place-name lookup) plus the survey number; add sub_division only when the user wants one specific split confirmed. Rural and urban parcels both work. 1 credit. Costs 1 credit per call, waived when nothing is found.

post/api/v1/tools/subdivision_list

Request

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

Request body

rev_district_codestring required

Revenue district code

rev_taluk_codestring required

Revenue taluk code

rev_village_codestring required

Revenue village code (town code for an urban parcel)

survey_numberstring required

Survey number without the subdivision, e.g. 178

sub_divisionstring

Optional: one subdivision to confirm, e.g. 1C. The full list is returned either way.

register'rural' | 'urban'

Which register the codes belong to (the "register" the place-name lookup returned, or a parcel's rural_urban). Pass it: a taluk's village and town codes overlap.

ward_codestring

Town survey only: the ward (from the located parcel, the patta or the TSLR extract). A town survey number repeats across blocks, each a different parcel, so without the block the answer names the blocks and asks.

block_codestring

Town survey only: the block, same sources as ward_code.

Response

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

Changes

No recorded changes to this operation across all 1 revision of this API.