8 Service APIs

This section provides a reference for APIs that should be implemented by this Building Block.

The APIs defined here establish a blueprint for how the Building Block will interact with other Building Blocks. Additional APIs may be implemented by the Building Block, but the listed APIs define a minimal set of functionality that should be provided by any implementation of this Building Block.

The GovStack non-functional requirements document provides additional information on how 'adaptors' may be used to translate an existing API to the patterns described here. This section also provides guidance on how candidate products are tested and how GovStack validates a product's API against the API specifications defined here.

The tests for the Digital Registries Building Block can be found in this GitHub repository.

The Digital Registries Building Block may contain multiple registries/databases. The dynamic nature of the database structure requires a standard set of automatically generated APIs for all databases hosted on the platform. The system generates default API method endpoints automatically after each publication of the database schema. A new API service version is generated after each schema publish. Database schema version and API versions are in sync.

The naming convention and structure of the API endpoint are the following:

/{information type}/{registry acronym or code}/{version}/{API method as a name}.

Example 1: ​/api/data​/cr​/1.0​/create

Example 2: ​/api/v1/database/modify

Each registry contains a unique set of data and the Building Block enables an Analyst to change the data storage structure/schema on the fly. In the following example API descriptions are generated for one example dataset for the Postpartum Infant Care Program registry, where the Caretaker and infant child are registered and a registration ID is issued.

Example registry database logical data model.

Example registry database Json schema.

Digital Registries Building Block is expected to host the following API services for each database hosted on the platform.

The API is built using a representational state transfer (REST) software architectural style and described in Open API 3 standard using YAML (a human-readable data-serialization language). Request and response body is in JSON (lightweight data-interchange format).

8.1 Administrative/Analyst Functions

8.2 Applicant Functions

API endpoint that allows user to get database information with schema

GET/database/{id}

Authorization

apiKey

Path parameters

id*integer

Id of the database that schema is requested

Header parameters

Response

200

Body

application/json

idinteger

Database ID

versionstring

Database version number

namestring

Database name

descriptionstring

Database description

institutionstring

Owner of the database (institution)

numberFormatstring

Number format in database

schemaDatabaseSchema (object)

Schema object describing the database

schemaTagsarray of object

List of different schema tags that are related to the database

schemaFlagsarray of object

List of different schema flags that are related to the database

fieldsUniquesarray of array of string

isDraftboolean

Shows database draft status (is draft true/false)

isDisabledboolean

Shows if database is disabled or not

isArchivedboolean

Shows if database is archived or not

modifiedAtstring

Shows database last modification time

byUserNamestring

Shows user name of a person who created the database

byUserAuthIdinteger

Shows id of a person who created the database

byOnBehalfOfUserAuthIdinteger

Shows user id whose behalf was this database created

byOnBehalfOfUserNamestring

Shows user name whose behalf was this database created

generic_Servicesarray of object

List of possible API services for this database

dataIndexIncrementinteger

Shows database increment

hasLogoboolean

Shows if this database has logo or not

Request

JavaScriptCurl

const response = await fetch('/database/{id}', {
    method: 'GET',
    headers: {},
});
const data = await response.json();

Response

{
  "id": 353,
  "version": "2.7",
  "name": "MCTS",
  "description": "Database holding information about MCTS objects",
  "institution": "Ministry of Social Affairs",
  "numberFormat": "{code}{indexNoByCode}",
  "schema": {
    "type": "object",
    "properties": {
      "ID": {
        "type": "string",
        "triggers": [
          {
            "conditions": [
              {
                "logic": "==",
                "value": "text",
                "gate": "&&"
              }
            ],
            "actions": [
              {
                "type": "set-value",
                "value": "MCTS{indexNoByCode}",
                "field_id": 1
              }
            ]
          }
        ],
        "primaryKey": true,
        "readOnly": true,
        "description": "Registration ID",
        "example": "MCTS31",
        "id": 1
      },
      "child": {
        "type": "string",
        "properties": {
          "id": {
            "type": "string",
            "description": "Child ID",
            "example": "ID2",
            "id": 13
          }
        }
      }
    },
    "incrementIndex": 20,
    "required": [
      "ID"
    ]
  },
  "schemaTags": [
    {
      "name": "text",
      "path": "/Child/Citizenship",
      "isFulltext": true
    }
  ],
  "schemaFlags": [
    {
      "name": "mandatory",
      "path": "/ID"
    }
  ],
  "fieldsUniques": [
    [
      "text"
    ]
  ],
  "isDraft": false,
  "isDisabled": false,
  "isArchived": false,
  "modifiedAt": "2021-10-03T08:35:01.775915Z",
  "byUserName": "ingmar.dev",
  "byUserAuthId": 1,
  "byOnBehalfOfUserName": "text",
  "generic_Services": [
    {
      "serviceId": 1,
      "name": "data-create",
      "isVisible": true
    }
  ],
  "hasLogo": false
}

API endpoint that allows user to create or modify database schema

POST/database/modify

Header parameters

Body

application/json

groupNamestring

Group name where this schema is located

catalogNamestring

Catalog name where this schema is located

codestring

Short code of the database

schemaall of

Response

200

Success

Body

application/json

typestring

propertiesobject

incrementIndexinteger

requiredarray of string

Request

JavaScriptCurl

const response = await fetch('/database/modify', {
    method: 'POST',
    headers: {
      "Content-Type": "application/json"
    },
    body: JSON.stringify({}),
});
const data = await response.json();

Response

{
  "type": "object",
  "properties": {
    "ID": {
      "type": "string",
      "triggers": [
        {
          "conditions": [
            {
              "logic": "==",
              "value": "text",
              "gate": "&&"
            }
          ],
          "actions": [
            {
              "type": "set-value",
              "value": "MCTS{indexNoByCode}",
              "field_id": 1
            }
          ]
        }
      ],
      "primaryKey": true,
      "readOnly": true,
      "description": "Registration ID",
      "example": "MCTS31",
      "id": 1
    },
    "child": {
      "type": "string",
      "properties": {
        "id": {
          "type": "string",
          "description": "Child ID",
          "example": "ID2",
          "id": 13
        }
      }
    }
  },
  "incrementIndex": 20,
  "required": [
    "ID"
  ]
}

API endpoint that allows user to delete database schema

DELETE/database/{id}

Authorization

apiKey

Path parameters

id*integer

Id of the database that schema is requested

Header parameters

Response

200

Success

Body

application/json

string

Request

JavaScriptCurl

const response = await fetch('/database/{id}', {
    method: 'DELETE',
    headers: {},
});
const data = await response.json();

Response

"Success"

API endpoint that allows user to get information about all databases

GET/databases

Authorization

apiKey

Header parameters

Response

200

Body

application/json

any

Request

JavaScriptCurl

const response = await fetch('/databases', {
    method: 'GET',
    headers: {},
});
const data = await response.json();