New API Access on HDX: Tabular Data Endpoints · HDX Team
Source published: 26 May 2026
Read the original at OCHA Centre for Humanitarian DataWhat has changed
HDX has introduced Tabular Data Endpoints, giving supported datasets a queryable interface alongside downloadable files. Users can request selected rows and columns. Access requires an HDX API token, and participating datasets need suitable structures and maintenance.
The AIHI perspective
There is a wider lesson for NGO operations. If every report begins with downloading, renaming and reconciling files, the difficult work often sits between systems. An AI assistant placed on top of that process inherits the uncertainty. Begin by agreeing which information is authoritative, who maintains it and how another system should use it.
Map one handover
Choose a recurring report or approval. Follow one piece of information from its source to the person who acts on it. Record where it is copied, transformed or checked. Give each handover an owner and define how missing or conflicting information is handled. That becomes a focused integration brief.
Make freshness part of the answer
A useful operational view should make it possible to understand when information was updated, where it came from and who can resolve an exception. Those details help a reviewer decide whether to act. They also give future automation a clearer boundary.
Take one useful step.
- Name the authoritative source for one recurring report.
- Agree ownership, access and exception handling.
- Measure the manual handovers you can safely remove.
Original AIHI commentary. Source authorship remains with the credited publication.
Explore your AI readiness
