8 Service APIs
This section provides a reference for APIs that should be implemented by this Building Block.
Last updated
Was this helpful?
This section provides a reference for APIs that should be implemented by this Building Block.
Last updated
Was this helpful?
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.
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).
Searches (Regex supported) and returns multiple records as an array-list.
/data/{registryName}//{versionNumber}
Field for searching random string type data from database
John
Field name that user wishes to filter
FirstName
How user wishes to order the data
descending
Result page number
1
Number of results on one page
10
Example of searchable database field. If more searchable fields are in DB, then more similar fields will follow in input
Value can be in any supported format, for an example 'string'
Format is: INSTANCE/CLASS/MEMBER/SUBSYSTEM
eGovStack/GOV/90000009/digitalregistries
Searches and returns one record.
/data/{registryName}//{versionNumber}/read
Format is: INSTANCE/CLASS/MEMBER/SUBSYSTEM
eGovStack/GOV/90000009/digitalregistries
Updates one existing record in the registry database.
/data/{registryName}//{versionNumber}/update
Format is: INSTANCE/CLASS/MEMBER/SUBSYSTEM
eGovStack/GOV/90000009/digitalregistries
Search object that needs to be updated
Update found object with the following data
No body
Updates multiple records in the registry database that match the input query.
/data/{registryName}//{versionNumber}/updateEntries
Format is: INSTANCE/CLASS/MEMBER/SUBSYSTEM
eGovStack/GOV/90000009/digitalregistries
Find objects that needs to be updated
Data that needs to be added to the found objects
No body
API updates existing record if matching with input parameters is successful. If record is not found the API will create a new record.
/data/{registryName}//{versionNumber}/updateOrCreate
Format is: INSTANCE/CLASS/MEMBER/SUBSYSTEM
eGovStack/GOV/90000009/digitalregistries
Find object to update, if object not found, new will be created
Data that will be updated for found Example object. If object not found new object with this data is created
Searches records based on input parameters and returns boolean answer (true/false).
/data/{registryName}//{versionNumber}/exists
Format is: INSTANCE/CLASS/MEMBER/SUBSYSTEM
eGovStack/GOV/90000009/digitalregistries
Delete record.
/data/{registryName}//{versionNumber}//{id}/delete
ID of the citizen that needs to be deleted from the Registry data query API
ID1
Format is: INSTANCE/CLASS/MEMBER/SUBSYSTEM
eGovStack/GOV/90000009/digitalregistries
No body
Searches and returns one record’s one field value.
/data/{registryName}//{versionNumber}//{uuid}/readValue/{field}.{ext}
Primary key field
DB-1
Data format. Endpoint: /data/DB/1.0/DB-1/read-value/First%20name.json
First name
Data format. Endpoint: /data/DB/1.0/DB-1/read-value/First%20name.json
json
Format is: INSTANCE/CLASS/MEMBER/SUBSYSTEM
eGovStack/GOV/90000009/digitalregistries
Allows a user to see who has read their personal data.
/data/mypersonalDataUsage
User's personal unique identifier
EE378129277266
Database acronym
MCTS
Format is: INSTANCE/CLASS/MEMBER/SUBSYSTEM
eGovStack/GOV/90000009/digitalregistries
Searches (Regex supported) and returns multiple records as an array-list.
/data/{registryName}//{versionNumber}
Field for searching random string type data from database
John
Field name that user wishes to filter
FirstName
How user wishes to order the data
descending
Result page number
1
Number of results on one page
10
Example of searchable database field. If more searchable fields are in DB, then more similar fields will follow in input
Value can be in any supported format, for an example 'string'
Format is: INSTANCE/CLASS/MEMBER/SUBSYSTEM
eGovStack/GOV/90000009/digitalregistries
/data/mcts/createEntries
Format is: INSTANCE/CLASS/MEMBER/SUBSYSTEM
eGovStack/GOV/90000009/digitalregistries
Searches and returns one record.
/data/{registryName}//{versionNumber}/read
Format is: INSTANCE/CLASS/MEMBER/SUBSYSTEM
eGovStack/GOV/90000009/digitalregistries
API endpoint that allows user to get database information with schema
/database/{id}
Id of the database that schema is requested
1
Format is: INSTANCE/CLASS/MEMBER/SUBSYSTEM
eGovStack/GOV/90000009/eregistrations-dev
API endpoint that allows user to delete database schema
/database/{id}
Id of the database that schema is requested
1
Format is: INSTANCE/CLASS/MEMBER/SUBSYSTEM
eGovStack/GOV/90000009/eregistrations-dev
API endpoint that allows user to create or modify database schema
/database/modify
Format is: INSTANCE/CLASS/MEMBER/SUBSYSTEM
eGovStack/GOV/90000009/eregistrations-dev
Group name where this schema is located
Test
Catalog name where this schema is located
Mother and Child
Short code of the database
MCR
API endpoint that allows user to get information about all databases
/databases
Format is: INSTANCE/CLASS/MEMBER/SUBSYSTEM
eGovStack/GOV/90000009/eregistrations-dev