Water & Sewerage Service API
Last updated
Was this helpful?
Last updated
Was this helpful?
Citizen or employee can apply for new water connection.
/wc/_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 water connection
with newer details.
/wc/_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.
Get the water connections list based on the input parameters.
/wc/_search
Unique id for a tenant.
List of system generated ids of water connection.
List of water connection numbers to search..
List of old water connection numbers to search..
MobileNumber of owner whose water connection is to be searched.
Fetches properties with created time after fromDate.
Fetches properties with created time till toDate.
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.
Citizen or employee can apply for new Sewerage connection.
/swc/_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 Sewerage connection
with newer details.
/swc/_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.
Get the water connections list based on the input parameters.
/swc/_search
Unique id for a tenant.
List of system generated ids of Sewerage connection.
List of Sewerage connection numbers to search..
List of old Sewerage connection numbers to search..
MobileNumber of owner whose Sewerage connection is to be searched.
Fetches Sewerage Connection with created time after fromDate.
Fetches Sewerage Connection with created time till toDate.
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.