How to Scrape OCHA Humanitarian Funding Data

Export official OCHA FTS contributions and pledges with donor, recipient, plan, and cluster 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.

Model funding flows without losing meaning

Preserve the flow identifier, source organization, destination organization, plan or appeal, amount, currency, status, and reporting dates. A commitment, pledge, paid contribution, and transferred amount are not synonyms, so keep the published flow status alongside every value. Do not add amounts expressed in different currencies unless the API supplies a comparable USD value or you document a separate conversion. OCHA may revise or reclassify flows; use the stable record identifier for upserts and retain the collection time for auditability. Pagination should stop at the requested result bound even when the source advertises more records, keeping recurring exports predictable and affordable.