Land

Land APIs

API specs to create land registry applications, update, and search applications.

create

post
/v1/land/_create
Body

Contract class to receive request. Array of Land items are used in case of create . Where as single Land item is used for update

Responses
200

OK

*/*
post
/v1/land/_create

update

post
/v1/land/_update
Body

Contract class to receive request. Array of Land items are used in case of create . Where as single Land item is used for update

Responses
200

OK

*/*
post
/v1/land/_update

search

post
/v1/land/_search
Query parameters
idsstring[]Optional
landUIdstringOptional
limitinteger · int32Optional
localitystringOptional
mobileNumberstringOptional
offsetinteger · int32Optional
tenantIdstringRequired
userIdsstring[]Optional
Body
Responses
200

OK

*/*
post
/v1/land/_search

Apply for new building plan application.

post
/v1/bpa/_create

Citizen, Employee, Or an Architect can apply for new build plan approval

Body

Contract class to receive request. Array of Property items are used in case of create . Where as single Property item is used for update

Responses
post
/v1/bpa/_create

Update existing application.

post
/v1/bpa/_update

Updates a given application with newer details.

Body

Contract class to receive request. Array of Property items are used in case of create . Where as single Property item is used for update

Responses
post
/v1/bpa/_update

Get the list of application by passing the diffrent search criteria.

post
/v1/bpa/_search

Get the properties list based on the input parameters.

Query parameters
tenantIdstring · varcharRequired

Unique id for a tenant.

idsstring[]Optional

List of system generated ids of BPA applications.

edcrNumberstringOptional

edcr Number.

applicationNostringOptional

application numbers

mobileNumberinteger · int64Optional

MobileNumber of land owners

approvalNostringOptional

approval no

Body

RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.

apiIdstring · max: 128Required

unique API ID

verstring · max: 32Required

API version - for HTTP based request this will be same as used in path

tsinteger · int64Required

time in epoch

actionstring · max: 32Required

API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc

didstring · max: 1024Optional

Device ID from which the API is called

keystring · max: 256Optional

API key (API key provided to the caller in case of server to server communication)

msgIdstring · max: 256Required

Unique request message id from the caller

requesterIdstring · max: 256Optional

UserId of the user calling

authTokenstringOptional

//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token

correlationIdstringRead-onlyOptional
Responses
200

Successful response

*/*
post
/v1/bpa/_search

Last updated

Was this helpful?