Property Tax Service API
Last updated
Last updated
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Get the properties list based on the input parameters.
requestInfoWrapper
OK
requestInfoWrapper
OK
requestInfoWrapper
OK
Updates a given Property
with newer details.
propertyRequest
OK
requestInfoWrapper
OK
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
propertyRequest
OK
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
Details for the new property + RequestHeader meta data.
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.
Property created sucessfully
Property created sucessfully
The API will delete the property associated with the given propertyId from the system The API works in idempotent manner.
Request header for the property delete Request.
Info of the API being called
Contains information about the device used to access the api
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
This is acting ID token of the authenticated user on the server. Any value provided by the clients will be ignored and actual user based on authtoken will be used on the server.
Hash describing the current RequestHeader
Deleted Property successful
Deleted Property successful
Get the properties list based on the input parameters.
RequestHeader meta data.
Info of the API being called
Contains information about the device used to access the api
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
This is acting ID token of the authenticated user on the server. Any value provided by the clients will be ignored and actual user based on authtoken will be used on the server.
Hash describing the current RequestHeader
Successful response
Successful response
The API will delete the property associated with the given propertyId from the system The API works in idempotent manner.
Request header for the property delete Request.
Info of the API being called
Contains information about the device used to access the api
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
This is acting ID token of the authenticated user on the server. Any value provided by the clients will be ignored and actual user based on authtoken will be used on the server.
Hash describing the current RequestHeader
Deleted Property successful
Deleted Property successful
Updates a given Property
with newer details.
Request header for the property Request.
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.
Update Property successful
Update Property successful