Faecal Sludge Management (FSM)
Last updated
Was this helpful?
Last updated
Was this helpful?
Gets the list of fsm application for a particular ULB based on search criteria.
/fsm/v1/_search
Unique id for a tenant.
Search by list of UUID
search application by list of application Status(s)
search application by list of Locality (s)
search by list of uuid(s) of the owner of the application
search by the created date faling between the fromdate and today
search by the created date faling between the fromdate and today
search application by list of applicationNo(s)
Search applicationb by mobileNumber of the Owner of the application
offset for the pagination results
limit for the pagination results
sort the search results in Ascending or descending order
ASC
, DESC
sort the search results by fields
applicationStatus
, applicationNumber
, propertyUsage
, vehicle
, locality
, createdTime
/fsm/v1/_audit
Unique id for a tenant.
search for audit log based on the application no of FSM
search for audit log based on the unique id of the application
Apply for desludging
/fsm/v1/_create
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.
Request schema of FSM application.
BPA application object to capture the details of land, land owners, and address of the land.
Updates service request
/fsm/v1/_update
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.
Request schema of FSM application.
BPA application object to capture the details of land, land owners, and address of the land.
/fsm/v1/_plainsearch
applicationNumber
, applicationStatus
, createdTime
, locality
, propertyUsage
, vehicle
ASC
, DESC
/fsm-calculator/v1/billingSlab/_create
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.
Representation of billing slab
/fsm-calculator/v1/billingSlab/_update
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.
Representation of billing slab
/fsm-calculator/v1/billingSlab/_search
Unique id for a tenant.
offset for the pagination results
limit for the pagination results
sort the search results in Ascending or descending order
ASC
, DESC
sort the search results by fields
id
, propertyType
, capacity
serch by ids of the billingslab
search by propertyType
search by capacity
search by slum yes or no
YES
, NO
/fsm-calculator/v1/_calculate
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.
Calculation Criteria to calcaulte and generate Demand
/fsm-calculator/v1/_estimate
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.
Calculation Criteria to calcaulte and generate Demand