OCHA Humanitarian Funding Scraper

Export official contribution, commitment, and pledge flows from the UN OCHA Financial Tracking Service. The Actor calls the public FTS JSON API directly and normalizes donors, recipients, plans, clusters, dates, descriptions, and USD amounts.

What you get

• One dataset row per published humanitarian funding flow
• Donor and recipient organizations, budget year, amount, status, and plan context
• Stable flow identifiers and direct OCHA source links for verification
• Bounded pagination, transient-error retries, and inexpensive 256 MB execution

Output fields

Typical fields include id, amountUSD, budgetYear, date, description, status, sourceOrganizations, destinationOrganizations, plans, clusters, source_url, and source.

Example output

{"id":12345,"amountUSD":500000,"budgetYear":2025,"description":"Emergency response contribution","sourceOrganizations":[{"name":"Example donor"}],"destinationOrganizations":[{"name":"Example recipient"}],"source_url":"https://fts.unocha.org/flows/12345"}

Input parameters

Parameter	Description
year	Funding-flow budget year to query.
organizationId	Optional OCHA organization identifier.
planId	Optional Humanitarian Response Plan identifier.
maxResults	Maximum flows saved and charged.

Use cases

Humanitarian funding dashboards, donor analysis, appeal monitoring, pledge-versus-commitment research, aid-flow archives, newsroom investigations, and scheduled finance feeds.

Limitations

Flow statuses have different meanings and should not be combined without a documented rule. OCHA may revise historical records. Organization and plan filters require numeric FTS identifiers. The Actor exports the published data and does not determine whether a commitment has been disbursed or judge funding effectiveness.

Compared to alternatives

Most OCHA FTS data on the Store ships as a static or periodically refreshed export. This Actor queries the live FTS API on each run, so dashboards and monitors always see current donor, recipient, and plan records rather than a stale snapshot. Pair it with UNHCR Refugee Data Scraper for displacement context alongside funding flows. Browse all Thirdwatch Actors or read the Thirdwatch OCHA guide.

FAQ

Does the Actor require OCHA credentials? No. It uses the public FTS API.

Can I schedule a donor or plan monitor? Yes. Save the input as an Apify Task and attach a schedule or webhook.

Open the input form or review recent runs.

Funding records need contextual interpretation. Verify material decisions against OCHA FTS. This independent Actor is not affiliated with or endorsed by the United Nations or OCHA.

Last verified: 2026-07