Version:
v 2.1.1
Release Date:
May 8, 2024
Bug Fixes
Subareas Empty Result Handling: Previously, when the result for subareas was empty, the system was throwing an exception. This has been fixed in this release. Now, when the result is empty, the system will return an empty response instead of an error.
Post Request Parameter Issue: There was an issue with the post request where the system was indicating that the 'Ancestor' parameter was missing. This issue has been resolved in this release.
Version:
v 2.1
Release Date:
March 28, 2024
New Features:
Configs Endpoint: A new endpoint /api/v2/configs has been added. This endpoint allows users to download and persist the TOML configuration file to the resource folder. The configuration file is now externalized as a private GitHub repository. The country's level information from the configuration file is used for later queries.
Stats Information: Stats information has been added to the output json. This includes matchesTotal, matchesNull, and matchesNoNull. To generate these stats, users need to pass a new parameter stats=true. This feature is only available for the area and subAreas endpoints.
Version:
v 2.0 (initial release)
Release Date:
February 1, 2024
New Features:
Locators Endpoint: The /api/v2/locators endpoint supports both GET and POST methods. It returns all the facilities matching the provided search criteria.
Providers Endpoint: The /api/v2/providers endpoint supports the GET method. It returns a list of providers working in the facility.
Areas Endpoint: The /api/v2/areas endpoint supports both GET and POST methods. It returns all the areas within the country.
SubAreas Endpoint: The /api/v2/subAreas endpoint supports both GET and POST methods. It returns all the subareas within the country and the area.
Proxy Images Endpoint: The /api/v2/proxy/images/{resourceId} endpoint supports the GET method. It fetches the image from the DHIS2 server and returns that image.
FHIR Format Support: The API now provides an option to download the results in FHIR format.
Spring Boot Framework: This version of the API is built upon the Spring Boot framework, providing enhanced performance and scalability.
API Documentation: The API documentation has been implemented using Swagger and can be generated using the /api/v2/docs endpoint.
Bug Fixes:
No bug fixes in this release as this is the initial release.
Known Issues:
No known issues at the time of this release.