Property Tax APIs

Create New Property

Creates new property.

post
/property/_create

Creates new property with basic information related to land and owner information. Can be integrated with other modules like Water and Sewerage or Trade License to act as base entity against which water connection or trade license can be issued

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
201

Property created sucessfully

text/plain
Responseobject

Property created sucessfully

post
/property/_create

Update Existing Property

Update existing property.

post
/property/_update

Updates a given Property 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
/property/_update

Fetch Properties List

Get the list of properties defined in the system.

post
/property/_search

Get the properties list based on the input parameters.

Query parameters
tenantIdstringRequired

Unique id for a tenant.

namestring | nullableOptional

Name of owner whose property is to be searched.

idsstringOptional

List of system generated ids of properties.

constructionDetailNumbersstring · min: 4 · max: 128Optional

List of constructionDetailNumbers to search.

oldpropertyidsstring · min: 4 · max: 128Optional

List of oldPropertyIds to search..

mobileNumberinteger · int64Optional

MobileNumber of owner whose property is to be searched.

fromDatenumber · doubleOptional

Fetches properties with created time after fromDate.

toDatenumber · doubleOptional

Fetches properties with created time till toDate.

Body

RequestHeader should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestHeader 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 ResponseHeader in the response body to ensure correlation.

tsinteger · int64Required

time in epoch

actionstring · max: 32Required

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

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

correlationIdstringOptional
signaturestringOptional

Hash describing the current RequestHeader

Responses
post
/property/_search

Delete Existing Property

Delete existing property.

post
/property/_delete

The API will delete the property associated with the given propertyId from the system The API works in idempotent manner.

Query parameters
tenantIdstringRequired

Unique id for a tenant.

propertyIdstring · min: 4 · max: 128Required

The properrtyId to be deactivated

Body

RequestHeader should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestHeader 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 ResponseHeader in the response body to ensure correlation.

tsinteger · int64Required

time in epoch

actionstring · max: 32Required

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

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

correlationIdstringOptional
signaturestringOptional

Hash describing the current RequestHeader

Responses
post
/property/_delete

Cancel Existing Property

Cancel existing property.

post
/property/_cancel

The API will delete the property associated with the given propertyId from the system The API works in idempotent manner.

Query parameters
tenantIdstringRequired

Unique id for a tenant.

propertyIdstring · min: 4 · max: 128Required

The properrtyId to be deactivated

Body

RequestHeader should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestHeader 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 ResponseHeader in the response body to ensure correlation.

tsinteger · int64Required

time in epoch

actionstring · max: 32Required

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

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

correlationIdstringOptional
signaturestringOptional

Hash describing the current RequestHeader

Responses
post
/property/_cancel

Last updated

Was this helpful?