> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/sanitation/water-sanitation-product-suite/waste-management-system/faecal-sludge-management-fsm/enablement-toolkits-assetization-for-fsm/data-loading-steps/loading-vendor-vehicle-and-driver-data.md). # Loading Vendor,Vehicle and Driver Data Ways to load Vendor details : * From Api * By FSM Registry **Loading from API :** Steps: 1. Import this collection - 2. Change the request url specific to environment. For Create DSO(URL) : For Search DSO(URL) : [https://sujog-dev.odisha.gov.in/vendor/v1/\_search?tenantId=od.anandapur](https://sujog-dev.odisha.gov.in/vendor/v1/_search?tenantId=od.nimapara) For Update DSO(URL) : [https://sujog-dev.odisha.gov.in/vendor/v1/](https://sujog-dev.odisha.gov.in/vendor/v1/_create)[\_update?tenantId=od.anandapur](https://sujog-dev.odisha.gov.in/vendor/v1/_search?tenantId=od.nimapara) 3. Login from FSM\_ADMINDEV credentials(for sujog-dev) which is having FSM Admin role for all the ulb’s. 4. Copy the auth token. Paste the auth token in the req. Body “authToken” field. 5. Request Info (eg. anandapur ulb) for Create DSO :-\
```json { "RequestInfo": { "apiId": "Rainmaker", "authToken": "453cf29c-58de-4e47-9821-91f39e2dde3e", "userInfo": { "id": 3186071, "uuid": "2f3851cd-864e-42d7-869c-d5a05abb8f39", "userName": "FSM_ADMINDEV", "name": "Taresh", "mobileNumber": "7721827042", "emailId": null, "locale": null, "type": "EMPLOYEE", "roles": [ { "name": "FSM Administrator", "code": "FSM_ADMIN", "tenantId": "od.anandapur" } ], "active": true, "tenantId": "od.anandapur", "permanentCity": null }, "msgId": "1660805524793|en_IN" }, "vendor": { "tenantId": "od.anandapur", "name": "NIPS", "agencyType": "ULB", "paymentPreference": "post-service", "address": { "tenantId": "od.anandapur", "doorNo": "my door", "plotNo": "my plot", "landmark": "my landmark", "city": "anandapur", "district": "anandapur", "region": "anandapur", "state": "odisha", "country": "in", "pincode": "143001", "additionDetails": null, "buildingName": "my building", "street": "my streat", "locality": { "id": 2, "name": "Padampur", "localname": "Padampur", "longitude": null, "latitude": null, "label": "Locality", "code": "VIL1", "children": [] }, "geoLocation": { "latitude": 0, "longitude": 0, "additionalDetails": {} } }, "owner": { "tenantId": "od.anandapur", "name": "NIPS", "fatherOrHusbandName": "NA", "relationship": "FATHER", "gender": "MALE", "dob": 550261800000, "emailId": "test@dso.test", "correspondenceAddress": "KPHB", "mobileNumber": 8908257220 }, "vehicles": [ { "tenantId": "od.anandapur", "registrationNumber": "OD09J7873", "model": "MAHINDRA", "type": "MAHINDRA.TRUCK1", "tankCapacity": "1000", "suctionType": "SEWER_SUCTION_MACHINE", "pollutionCertiValidTill": 1611584416772, "InsuranceCertValidTill": 1611584416772, "fitnessValidTill": 1611584416772, "roadTaxPaidTill": 1611584416772, "gpsEnabled": true, "source": "Municipal records", "status": "ACTIVE", "vendorVehicleStatus": "ACTIVE", "owner": { "tenantId": "od.anandapur", "name": "NIPS", "fatherOrHusbandName": "NA", "relationship": "FATHER", "gender": "MALE", "dob": 550261800000, "emailId": "test@dso.test", "correspondenceAddress": "KPHB", "mobileNumber": 8908257220 } } ], "drivers": [ { "tenantId": "od.anandapur", "name": "DIPU MUKHI", "licenseNumber": "OR0920040025878", "status": "ACTIVE", "owner": { "tenantId": "od", "name": "DIPU MUKHI", "fatherOrHusbandName": "NA", "relationship": "OTHER", "gender": "MALE", "dob": -19800000, "emailId": "abc@egov.com", "mobileNumber": "6371957727" }, "vendorDriverStatus": "ACTIVE" } ], "source": "WhatsApp" } } ``` **Note:** 1. *Before pushing the vendor,first add Vehicle in MDMS. Take Vehicle Make, Model and Capacity from* [*VehicleMakeModel*](https://github.com/egovernments/egov-mdms-data/blob/v2.3-patch/data/pg/Vehicle/VehicleMakeModel.json) *in MDMS.* 2. ***No special characters** allowed in Vendor name.* 3. *Vehicle Registration number should be **unique** for every vehicle.* 4. *Scenerios for Vendor and Vehicle users:*\ *- One Vendor can be linked with two or more vehicles.*\ *- One Vehicle is linked with One Vendor.*\ *- Two Vendors can’t have same mobile number because vendor is a user and user is stored uniquely in database.*\ *- Vendor owner, Vehicle owner and Driver owner can be same or different for One Vehicle.*\
5. Hit the url it’ll push the data of vendor. **From FSM Registry :** Add details of Cesspool Operator,Vehicle and Driver from FSM Registry and link Vehicle with Cesspool operator and Driver with Cesspool Operator. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.digit.org/sanitation/water-sanitation-product-suite/waste-management-system/faecal-sludge-management-fsm/enablement-toolkits-assetization-for-fsm/data-loading-steps/loading-vendor-vehicle-and-driver-data.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.