# OCHA Humanitarian Funding Scraper - FTS Aid Flows (`thirdwatch/ocha-humanitarian-funding-scraper`) Actor

Export official UN OCHA Financial Tracking Service funding flows, pledges, donors, recipients, plans, clusters, amounts, dates, and source links. Built for research, diligence, and market intelligence. No login, cookies, or API keys — clean JSON output and pay-per-result pricing.

- **URL**: https://apify.com/thirdwatch/ocha-humanitarian-funding-scraper.md
- **Developed by:** [Thirdwatch](https://apify.com/thirdwatch) (community)
- **Categories:** Business, Education
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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

```json
{"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

Direct official-API access avoids brittle page scraping and proxy costs. Pricing starts at $2 per 1,000 saved flows and falls to $1 per 1,000 at the GOLD tier. Try the [OCHA Humanitarian Funding Scraper](https://apify.com/thirdwatch/ocha-humanitarian-funding-scraper), browse [all Thirdwatch Actors](https://apify.com/thirdwatch), or read the [Thirdwatch OCHA guide](https://thirdwatch.dev/actors/ocha-humanitarian-funding-scraper).

### 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](https://apify.com/thirdwatch/ocha-humanitarian-funding-scraper?tab=input) or review [recent runs](https://apify.com/thirdwatch/ocha-humanitarian-funding-scraper?tab=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

# Actor input Schema

## `year` (type: `integer`):

Funding-flow budget year to query.

## `organizationId` (type: `integer`):

Optional OCHA organization identifier.

## `planId` (type: `integer`):

Optional Humanitarian Response Plan identifier.

## `maxResults` (type: `integer`):

Maximum number of flows to save and charge.

## Actor input object example

```json
{
  "year": 2025,
  "maxResults": 10
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("thirdwatch/ocha-humanitarian-funding-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("thirdwatch/ocha-humanitarian-funding-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call thirdwatch/ocha-humanitarian-funding-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,thirdwatch/ocha-humanitarian-funding-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ngHPl5pE5jSY7b1xb/builds/dnjgzstbkJ3jgyQiF/openapi.json