Master Data Management

Master Data Management APIs

Fetch master data for specific tenants and modules.

Get list of masters for a particular module and tenantId.

post

Get list of masters for a perticulare module and tenantId.

Body

Responses

201

Designation created sucessfully.

*/*

400

Invalid input.

*/*

post

HTTPcURLJavaScriptPython

POST /v1/_search HTTP/1.1
Host: egov-mdms-service
Content-Type: */*
Accept: */*
Content-Length: 501

{
  "RequestInfo": {
    "apiId": "text",
    "ver": "text",
    "ts": 1,
    "action": "text",
    "did": "text",
    "key": "text",
    "msgId": "text",
    "requesterId": "text",
    "authToken": "text",
    "userInfo": {
      "tenantId": "text",
      "id": 1,
      "userName": "text",
      "mobile": "text",
      "email": "text",
      "primaryrole": [
        {
          "name": "text",
          "description": "text"
        }
      ],
      "additionalroles": [
        {
          "tenantId": "text",
          "roles": [
            {
              "name": "text",
              "description": "text"
            }
          ]
        }
      ]
    }
  },
  "MdmsCriteria": {
    "tenantId": "text",
    "moduleDetails": [
      {
        "moduleName": "text",
        "masterDetails": [
          {
            "name": "text",
            "filter": "text"
          }
        ]
      }
    ]
  }
}

{
  "ResponseInfo": {
    "apiId": "text",
    "ver": "text",
    "ts": 1,
    "resMsgId": "text",
    "msgId": "text",
    "status": "SUCCESSFUL"
  },
  "mdms": [
    [
      {}
    ]
  ]
}

search

post

Query parameters

moduleNamestringRequired

moduleName

masterNamestringRequired

masterName

filterstringOptional

filter

tenantIdstringRequired

tenantId

Body

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.

apiIdstring · max: 128Required

unique API ID

verstring · max: 32Required

API version - for HTTP based request this will be same as used in path

tsinteger · int64Required

time in epoch

actionstring · max: 32Required

API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc

didstring · max: 1024Optional

Device ID from which the API is called

keystring · max: 256Optional

API key (API key provided to the caller in case of server to server communication)

msgIdstring · max: 256Required

Unique request message id from the caller

requesterIdstring · max: 256Optional

UserId of the user calling

authTokenstringOptional

//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token

correlationIdstringRead-onlyOptional

Responses

200

OK

*/*

Responseobject

201

Created

401

Unauthorized

403

Forbidden

404

Not Found

post

HTTPcURLJavaScriptPython

POST /v1/_get?moduleName=text&masterName=text&tenantId=text HTTP/1.1
Host: egov-mdms-service
Content-Type: application/json
Accept: */*
Content-Length: 360

{
  "apiId": "text",
  "ver": "text",
  "ts": 1,
  "action": "text",
  "did": "text",
  "key": "text",
  "msgId": "text",
  "requesterId": "text",
  "authToken": "text",
  "userInfo": {
    "tenantId": "text",
    "id": 1,
    "userName": "text",
    "mobile": "text",
    "email": "text",
    "primaryrole": [
      {
        "name": "text",
        "description": "text"
      }
    ],
    "additionalroles": [
      {
        "tenantId": "text",
        "roles": [
          {
            "name": "text",
            "description": "text"
          }
        ]
      }
    ]
  }
}

{}