HDX HAPI Changelog

HDX HAPI is built on several interconnected codebases:

hdx-hapi: provides the API endpoints, API documentation, and ReadTheDocs
hapi-sqlalchemy-schema: defines the schema for the underlying database
hapi-pipelines handles data collection and transformation from HDX, populating the database with structured datasets
hapi-pipelines-prod, a clone of hapi-pipelines used for deployment

Below we outline the major changes and updates to the production version of the API.

Latest changes

Aligned category and sub-category endpoint names in the docs with HDX data grids
affected-people/refugees -> affected-people/refugees-persons-of-concern
coordination-context/conflict-event -> coordination-context/conflict-events
food/food-security -> food-security-nutrition-poverty/food-security
food/food-price -> food-security-nutrition-poverty/food-prices-market-monitor
population-social/poverty-rate -> food-security-nutrition-poverty/poverty-rate
population-social/population -> geography-infrastructure/baseline-population
Note that the new endpoints are being released under v2 of the api and previous versions are maintained under v1

Increased temporal coverage for humanitarian needs subcategory
Increased geographical coverage to all available for operational presence subcategory

Increased geographical coverage to global for baseline population and poverty rate subcategories

Gender, age, and disability disaggregation in humanitarian needs reduced to a single freeform category column
Switch from using Cadre Harmonisé to IPC for food security data. This change entails that geographical coverage is expanded to global, and involves p-coding the administrative names.
Added provider_admin1_name and provider_admin2_name columns