Property Tax APIs
Create New Property
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
Contract class to receive request. Array of Property items are used in case of create . Where as single Property item is used for update
Property created sucessfully
Property created sucessfully
Property(s) creation failed
Update Existing Property
Updates a given Property with newer details.
Contract class to receive request. Array of Property items are used in case of create . Where as single Property item is used for update
Update Property successful
Update Property failed
Fetch Properties List
Get the properties list based on the input parameters.
Unique id for a tenant.
Name of owner whose property is to be searched.
List of system generated ids of properties.
List of constructionDetailNumbers to search.
List of oldPropertyIds to search..
MobileNumber of owner whose property is to be searched.
Fetches properties with created time after fromDate.
Fetches properties with created time till toDate.
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.
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
Hash describing the current RequestHeader
Successful response
Invalid input.
Delete Existing Property
The API will delete the property associated with the given propertyId from the system The API works in idempotent manner.
Unique id for a tenant.
The properrtyId to be deactivated
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.
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
Hash describing the current RequestHeader
Deleted Property successful
Delete Property failed
Cancel Existing Property
The API will delete the property associated with the given propertyId from the system The API works in idempotent manner.
Unique id for a tenant.
The properrtyId to be deactivated
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.
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
Hash describing the current RequestHeader
Deleted Property successful
Delete Property failed
Last updated
Was this helpful?