Property Tax Calculator
Last updated
Was this helpful?
Last updated
Was this helpful?
/propertytax/_updatedemand
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.
/propertytax/mutation/_calculate
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.
Estimates the Property Tax to be paid for given property .
/propertytax/_estimate
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.
Calculate Property Tax based on criteria.
/propertytax/_calculate
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.
Generates bill for payment.
/propertytax/_getbill
Unique id for a tenant.
Primary key of Property object.
Unique id of the assessment.
Year for which the property is being assessed, assessment year should be given in yyyy-yy format (2013-14).
Primary key of bill object.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
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.
/propertytax/v2/_estimate
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.
Get the properties list based on the input parameters.
/billingslab/_search
Unique id for a tenant.
True will be set in cases where only active properties are needed and False will be set when inactive properties are needed and no value will be set when all properties are needed.
Primary key of Property object.
The unique reference number for a property.
The unique old assessment no for a Property.
Locality boundary where the property is located.
The acknowldgement number no for a property.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
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.
API to create new properties.
/billingslab/_create
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.
Updates a given Property
with newer details.
/billingslab/_update
Unique ulb identifier
unique identifier of the billing slab uuid
Based on property type charges will change.
Based on property type charges will change.
Floor Number.
Floor Number.
Floor Number.
Floor Number.
Floor Number.
Floor Number.
Floor Number.
Floor Number.
Floor Number.
Floor Number.
Floor Number.
Floor Number.
/billingslab/mutation/_create
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.
/billingslab/mutation/_search
Unique Identifier(UUID) of the land for internal reference.
market value of the item
one of different categories of legal ownership
defined by the type of ownership, which can be determined by the legal description or how the property is deeded
value for dwelling configuration of the property
subOwnerShipCategory of product
Unique ULB identifier.
category of product usage
usageCategoryMinor
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
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.
/billingslab/mutation/_update
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.