> 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/public-finance/v2.3/exemplar/ifix-adapter/adapter-service-documents/ifix-adapter-master-data-service.md).
# iFIX Adapter Master Data Service
## Overview
Adapter master data service maintains information on Department, Expenditure and Projects. We can create these details and search for the same details based on the given parameters/request data.
### Version
Current version : 1.0.0
## Pre-requisites
Before we proceed with the configuration, make sure the following pre-requisites are met
1. Java 8
2. MongoDB instance
3. Required service dependency - Department entity service
## Features
It creates secure endpoints for the master data service. The access token is required to create any master data. The subsequent sections on this page discuss the service details maintained by the master data service.
### Department
Maintains the create and search department details. The following information is passed while creating the department - the Government ID, department code, department name, parent department if any. Searching the department details is on given parameters like IDs, Government ID, department code, department name.
### **API List**
| **Title** | **Link** |
| ----------------------- | ------------------------------------------------------------- |
| /department/v1/\_create | |
| /department/v1/\_search | |
### Expenditure
Maintains the expenditure details And provide create and search functionality. For creating the expenditure, the following details are required - the Government ID, the department ID, code, name, type (can be "SCHEME", "NON\_SCHEME") details. While searching the expenditure details, pass the given parameters like IDs, Government IDs, names, code.
### **API List**
| **Title** | **Link** |
| ------------------------ | ------------------------------------------------------------- |
| /expenditure/v1/\_create | |
| /expenditure/v1/\_search | |
### Project
Maintains the project details and provide create and search functionality. The following details are required to create the project - Government, name, code, expenditure ID, the department entity ID(s), location IDs. While searching, pass the IDs, Government ID, name, code, expenditure ID, location ID.
### **API List**
| **Title** | **Link** |
| -------------------- | ------------------------------------------------------------- |
| /project/v1/\_create | |
| /project/v1/\_search | |
## Interaction Diagram
## Environment
No environment-specific variables are required for the environment (migration).
## Configurations and Setup
Update the DB and URI configurations in the dev.yaml, qa.yaml, prod.yaml file.
## References and Notes
| **Title** | **Link** |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Swagger Yaml | [ReDoc Interactive Demo](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/egovernments/iFix-Dev/develop/domain-services/ifix-master-data-service/ifix-master-data-service-1.0.0.yaml#tag/COA/paths/~1chartOfAccount~1v1~1_search/post) |
| Postman collection | |
## Master Project API With Example
Project Create API creates the project when the Master data details (COA, Government, Expenditure, Department) and Department Entity have been created. COA And Government have to be created in iFIX core Master data service.
Project Create API takes the below attributes in request :
1. tenantId: This is the Id that will be defined while creating the Ifix core Master Government Service.
2. expenditureId: This is the Id that will be generated while creating the Adapter Master Expenditure Service.
3. code: This is the project code that needs to be created.
4. name: This is the project name that needs to be created.
5. departmentEntityIds: This is the Department Entity Ids. If we have to create a project at hierarchy level 1 then we need to pass the Department Entity Id of that corresponding level. It depends on the Department hierarchy level on which the project has to be created and hence the same level Department Entity [Id.](http://id.at/) You can pass a list of departmentEntityIds and can create the same project.
For reference, Below is a Dummy project create example:
Request :
```
{
"requestHeader": {
"ts": 1627193067,
"version": "2.0.0",
"msgId": "Unknown",
"signature": "NON",
"userInfo": {
"uuid": "e4fd96e8-3b6b-4e36-9503-0f14a01af39d"
}
},
"project": {
"tenantId": "pb",
"code": "7330_S557_DIV23SD02",
"name": "DOLOWAL UPPER",
"expenditureId": "13ef1c53-702d-43b5-9f97-43fa03c145c5",
"departmentEntityIds": ["295180a0-4d60-4805-a77f-92143bd115b4","901f76a8-1911-4960-b389-57b62bd4dcdb"
]
}
}
```
Response:
```
{
"responseHeader": {
"ts": 1627193067,
"correlationId": null,
"msgId": "Unknown",
"status": "successful",
"signature": "NON",
"version": "2.0.0"
},
"project": [
{
"id": "1fb13f0a-588f-476d-b839-afddae7980ef",
"tenantId": "pb",
"code": "7330_S557_DIV23SD02",
"name": "DOLOWAL UPPER",
"expenditureId": "13ef1c53-702d-43b5-9f97-43fa03c145c5",
"departmentEntityIds": [
"295180a0-4d60-4805-a77f-92143bd115b4",
"901f76a8-1911-4960-b389-57b62bd4dcdb"
],
"locationIds": null,
"auditDetails": {
"createdBy": "e4fd96e8-3b6b-4e36-9503-0f14a01af39d",
"lastModifiedBy": "e4fd96e8-3b6b-4e36-9503-0f14a01af39d",
"createdTime": 1646726943845,
"lastModifiedTime": 1646726943845
}
}
]
}
```
> [**](http://creativecommons.org/licenses/by/4.0/)*All content on this page by* [*eGov Foundation*](https://egov.org.in/) *is licensed under a* [*Creative Commons Attribution 4.0 International License*](http://creativecommons.org/licenses/by/4.0/)*.*
---
# 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/public-finance/v2.3/exemplar/ifix-adapter/adapter-service-documents/ifix-adapter-master-data-service.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.