Build a Humanitarian Funding Dashboard

Create a transparent aid-flow dashboard from OCHA FTS records without flattening away reporting context. The OCHA Humanitarian Funding Scraper provides a bounded connector to the authoritative publisher while preserving stable identifiers and source URLs on every row.

Start with a small, reviewable query

{"year":2025,"maxResults":1000}

Run a small sample before expanding the result limit. Inspect identifiers, dates, null values, units, qualifiers, and source fields in the Apify Dataset. Export as JSON for nested fields or CSV and Excel for review. For recurring ingestion, upsert on the publisher stable record dimensions instead of assuming every run is append-only.

Build a reliable data pipeline

The Actor uses direct HTTP requests, bounded inputs, transient-error retries, and explicit empty-result failures. It does not require a browser or paid proxy, so scheduled runs remain inexpensive. Keep the input in an Apify Task, send completion through a webhook, and load the dataset into a warehouse or dashboard. Store collection time downstream so source revisions can be distinguished from newly published records.

Interpret the source responsibly

Official publication does not remove the need for context. Preserve footnotes, status fields, dataset type, reporting period, and source attribution. A missing value is not zero, and a revised record is not necessarily a new event. For legal, medical, financial, safety, protection, or public-policy decisions, confirm material findings with the publisher and a qualified specialist.

This workflow is designed for aid organizations, donor analysts, and humanitarian finance teams. It is an independent integration and is not affiliated with or endorsed by the source institution.

Choose views that answer allocation questions

Organize the dashboard around four questions: how much is required, how much is funded, who provided it, and where it went. Pair an appeal-level funding ratio with tables for donors, recipient organizations, sectors, and destination countries. Keep pledges visually separate from committed or paid flows, and label the data timestamp prominently because finance records change throughout a response. Provide a drill-through to the original OCHA record instead of forcing users to trust an unexplained aggregate. A scheduled Task can refresh the underlying dataset daily while a warehouse snapshot records prior values for revision analysis.