> 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/sanitation-worker-welfare/vendor-registry.md).

# Vendor Registry

## Overview

As part of the worker welfare v1.0, a new worker registry concept is being introduced. The creation of a worker, updation of details, searching and tagging a worker for different operations on sanitation programmes will be covered. We will leverage the Individual Registry for storing and querying details about a worker. 

The individual service is an enhanced version of the user service that houses data about individuals. The individual service is being re-used from [DIGIT Health](https://health.digit.org/).

Click [here](https://health.digit.org/platform/architecture/low-level-design/registries/individual) to access the Individual Service.

## Architecture Diagram

<figure><img src="https://content.gitbook.com/content/XBU7xhTVuMJw3ncxgvWz/blobs/BL2TRJkEOC8YRTh5tku8/Screenshot%202023-09-22%20at%2010.30.37%20AM.png" alt=""><figcaption></figcaption></figure>

## Vendor Registry

#### Changes from Version 1.3.1 is 1.4.0

1. Change from driver concept to worker.
2. Deprecation of the driver table.
3. Backward compatibility for existing drivers (converting a driver user into an individual and mapping/backfilling to vendors).
4. Introducing worker vendor mapping.
5. Creation of workers directly using Individual registry APIs.

## API Specification

[Vendor\_Registration\_Contract.yaml](https://raw.githubusercontent.com/egovernments/SANITATION/sanitation_v1.4_api_contracts/API-CONTRACTS/fsm/Vendor_Registration_Contract.yaml?token=GHSAT0AAAAAACGUKWUFSEN4KJFWGCJW6P5OZINGSVA)

## ER Diagram

<figure><img src="https://content.gitbook.com/content/XBU7xhTVuMJw3ncxgvWz/blobs/H9Y097yZgJSKZUgW4Ldp/Screenshot%202023-09-22%20at%209.46.21%20AM.png" alt=""><figcaption></figcaption></figure>

## Sequence Diagram

#### **Create Worker**

<figure><img src="https://content.gitbook.com/content/XBU7xhTVuMJw3ncxgvWz/blobs/aE5tp5AWKJEmLeWVE8SM/Screenshot%202023-09-22%20at%209.47.13%20AM.png" alt=""><figcaption></figcaption></figure>

#### **Update Vendor**

<figure><img src="https://content.gitbook.com/content/XBU7xhTVuMJw3ncxgvWz/blobs/oDVbPg5fuNXO0RaPLUb1/Screenshot%202023-09-22%20at%209.48.03%20AM.png" alt=""><figcaption></figcaption></figure>


---

# 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/sanitation-worker-welfare/vendor-registry.md?ask=<question>&goal=<user_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.