# ReliefWeb Humanitarian & NGO Jobs Scraper | $3/1k, No API Key (`nomad-agent/reliefweb-scraper`) Actor

Scrape live humanitarian, NGO, aid-worker and UN-sector jobs from ReliefWeb (UN OCHA's job portal) — no API key or pre-approved appname needed. Title, organization, country, geo-coordinates, closing date, apply URL. Keyword/country filters, new-jobs-only monitoring, org enrichment. $0.003/job.

- **URL**: https://apify.com/nomad-agent/reliefweb-scraper.md
- **Developed by:** [Nomad.Dev](https://apify.com/nomad-agent) (community)
- **Categories:** Jobs
- **Stats:** 16 total users, 8 monthly users, 60.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.30 / 1,000 job 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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## ReliefWeb Humanitarian & NGO Jobs Scraper — No API Key Needed

Fetch current **humanitarian jobs, NGO jobs, aid-worker jobs and UN-sector vacancies** from ReliefWeb, the UN OCHA jobs portal, as clean JSON records.

> **Claude / Codex skill to describe and setup this actor: [SKILL.md](https://github.com/Exdenta/OinkAIJobSearch/blob/main/skill/reliefweb-scraper/SKILL.md)**

**Why this scraper:**

- **No API key, no approval process.** ReliefWeb's own API now requires a pre-approved `appname` before it accepts any request ([details](https://apidoc.reliefweb.int/parameters#appname)) — this Actor needs nothing: click Run and get jobs.
- **A third of the price** of the only other ReliefWeb scraper on the Store — **$0.003 per job** (volume discounts down to $0.0023) vs. $0.009 elsewhere.
- **Correctly categorized under JOBS**, so aid-sector recruiters actually find it when browsing the Store (the other ReliefWeb scraper is mis-tagged under AI/Automation/E-commerce).
- **Built-in keyword + country + freshness filters** — no need to hand it raw ReliefWeb URLs to get started; just click Run.
- **Handles ReliefWeb's datacenter-IP block for you** by fetching through a Residential proxy by default — reliability that a generic "proxy support" claim doesn't guarantee.
- Optional **new-jobs-only monitoring mode** for scheduled alerts and **organisation enrichment** (org website + description) as a paid add-on.

### What ReliefWeb jobs data does this scraper extract?

Each result is one flat JSON record per job posting:

| Field | Meaning |
|---|---|
| `id` | Stable source-side identifier (ReliefWeb job id) |
| `title` | Job title as posted |
| `company` | Hiring organisation, or `null` if not tagged |
| `country` | Country as published by ReliefWeb's own Country tag, or `null` |
| `location` | City + country combined for display (falls back to "Worldwide" / "Remote / Worldwide") |
| `latitude` | Approximate latitude of the posting's country (country centroid), or `null` |
| `longitude` | Approximate longitude of the posting's country (country centroid), or `null` |
| `url` | Direct link to the posting |
| `postedAt` | Posting date/time as published in the feed, or `null` |
| `deadline` | Application closing date (ISO `YYYY-MM-DD`), or `null` if the posting has no closing date |
| `salary` | Salary if the posting states one (ReliefWeb rarely does), else `null` |
| `orgWebsite` | Hiring organisation's homepage, when the *Enrich organisation* add-on is on, else `null` |
| `orgDescription` | Short organisation description, when the *Enrich organisation* add-on is on, else `null` |
| `snippet` | Short plain-text description excerpt |
| `source` | Always `"reliefweb"` |

### How to scrape ReliefWeb jobs with this Actor

1. Click **Try for free** / **Run** — no login to the target site, no cookies, no proxies to configure.
2. Adjust the input (`search`, `country`, `postedSince`, `maxItems`) or keep the defaults.
3. Run it and export the dataset as JSON, CSV or Excel, or read it over the [API](https://docs.apify.com/api/v2).

Run it from your own code:

```python
from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("nomad-agent/reliefweb-scraper").call(run_input={"maxItems": 50})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["title"], "—", item["company"], item["url"])
```

Or a single HTTP call that runs the Actor and returns items in one response:

```bash
curl -X POST \
  "https://api.apify.com/v2/acts/nomad-agent~reliefweb-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"maxItems": 50}'
```

### Input

| Field | Type | Default | Notes |
|---|---|---|---|
| `search` | string | `""` | Free-text query to filter the feed (e.g. "software engineer", "data", "IT digital"). Leave empty for all current openings. |
| `country` | string | `""` | Only return postings whose Country field contains this text (e.g. "Kenya"). Case-insensitive, partial match. Leave empty for all countries. |
| `postedSince` | integer | `0` | Only return postings published within this many days. Set 0 to disable. |
| `maxItems` | integer | `20` | Maximum number of job openings to return (the feed always returns roughly the 20 most recent postings per fetch, so values above 20 have no effect). Set 0 for no limit. Each result returned is billed. |
| `enrichOrganisation` | boolean | `false` | *(Paid add-on)* Follow up to each hiring organisation's ReliefWeb profile page and add `orgWebsite` + `orgDescription`. Each org is fetched at most once per run. Fields stay `null` when the profile doesn't expose them. |
| `monitoringMode` | boolean | `false` | Return only postings not seen in prior runs (state kept in the Actor's key-value store) — a "new jobs only" alert source for scheduled runs. |
| `resetMonitoringState` | boolean | `false` | One-shot: clear the remembered set before this run so every current posting counts as new again. Turn off afterwards. |
| `proxyConfiguration` | object (proxy) | Residential group | Proxy used to fetch the feed. Keep Residential selected — ReliefWeb blocks datacenter IPs. Overrides `useResidentialProxy` when set. |
| `useResidentialProxy` | boolean | `true` | **Deprecated** — use `proxyConfiguration` instead. Kept as a fallback for old callers when `proxyConfiguration` is not set. |
| `cacheTtlSeconds` | integer | `1800` | *(Advanced)* Reuse a previously fetched feed for this many seconds instead of re-fetching. Set 0 to always fetch fresh data. |

### Output example

```json
{
  "id": "4218889",
  "title": "Protection Officer",
  "company": "Danish Refugee Council",
  "country": "Ukraine",
  "location": "Ukraine",
  "latitude": 48.38,
  "longitude": 31.17,
  "url": "https://reliefweb.int/job/4218889/protection-officer",
  "postedAt": "Thu, 02 Jul 2026 12:30:09 +0000",
  "deadline": "2026-07-16",
  "salary": null,
  "orgWebsite": "https://drc.ngo",
  "orgDescription": "The Danish Refugee Council assists refugees and internally displaced persons...",
  "snippet": "DRC is looking for a Protection Officer...",
  "source": "reliefweb"
}
```

`orgWebsite` / `orgDescription` are populated only when the **Enrich organisation** add-on is enabled. Any field the source doesn't provide for a given posting (e.g. no closing date, no organisation tag, no stated salary) comes back as `null`, never an empty string.

### New postings only (monitoring mode)

Turn on **Monitoring mode** to get only postings that weren't returned by a prior run — the Actor remembers which job ids it has already emitted (in its key-value store) and skips them next time. Combined with a schedule, this turns the scraper into a "new humanitarian jobs only" alert source, so you never re-process the same posting. Use **Reset monitoring state** once to start the memory over (every current posting counts as new again), then switch it back off.

### Organisation enrichment (paid add-on)

ReliefWeb's raw jobs feed doesn't carry the hiring organisation's website or description. Enable **Enrich organisation** to have the Actor follow each posting to the organisation's ReliefWeb profile page and add `orgWebsite` and `orgDescription`. Each organisation is fetched at most once per run, and the fields stay `null` when the profile page doesn't expose them.

### Integrations

Export the dataset as JSON, CSV or Excel from the Console, or pull it programmatically: works out of the box with Make, Zapier and n8n, is callable via a single `run-sync-get-dataset-items` HTTP call (see below), and is usable from AI agents through the [Apify MCP server](https://apify.com/apify/actors-mcp-server).

### Pricing

Pay per event: **$0.005 per Actor start** and **just $0.003 per job returned** (volume discounts down to $0.0023/job on higher Apify plans) — a third of the per-job price of the only other ReliefWeb scraper on the Store ($0.009/job + $0.05/start).
A full default run (20 jobs) ≈ $0.065. No subscription, no rental — you pay only for what you fetch.
The optional **Enrich organisation** add-on is billed per enriched organisation (rate shown in the Console before you run); leave it off and you're never charged for it.
If you keep the default Residential proxy on, Apify also bills residential proxy bandwidth (GB) separately per your plan's proxy rates.

### Use cases

- Humanitarian-sector job boards and newsletters
- Deadline-aware alert bots for aid workers
- M\&E and surge-roster sourcing
- Research on humanitarian hiring by country

### FAQ

**Is it legal to scrape ReliefWeb jobs?**
This Actor reads only publicly available job postings — data any visitor can see without logging in. No personal data behind authentication is touched. Review the target site's terms and your local regulations for your specific use case.

**Do I need an account on the target site?**
No. Postings are fetched from public pages/APIs — no login, cookies or session tokens.

**Why not just use ReliefWeb's free API?**
The official API (api.reliefweb.int) is free, but it now rejects every request that doesn't carry a **pre-approved `appname`** — you have to apply and wait to be whitelisted. This Actor works instantly, and adds what the raw API doesn't give you: geo-coordinates per posting, organisation website/description enrichment, normalized ISO closing dates, and a new-jobs-only monitoring mode.

**How fresh is the data?**
Every run fetches live listings. Results are cached for `cacheTtlSeconds` (default 30 min, set 0 to always hit the source live).

**How many jobs can I get?**
The ReliefWeb jobs feed returns roughly the 20 most recent postings per fetch, newest first, and does not paginate further — `maxItems` (capped at 20) trims that down if you want fewer.

**Something broken or missing?**
Open an issue on the Actor's **Issues** tab — it is monitored and reliability fixes ship fast.

**Finding it useful?**
A quick review on the Actor's Store page helps other aid-sector folks find it — and tells us what to build next.

### Related Actors

- [UNjobs Scraper — unjobs.org UN Vacancies](https://apify.com/nomad-agent/unjobs-scraper)
- [Research & Academic Jobs Scraper — 10 Sources](https://apify.com/nomad-agent/researcher-bundle)
- [UN Careers Job Scraper — United Nations Jobs](https://apify.com/nomad-agent/un-careers-scraper)
- [Impactpool Jobs Scraper — UN & NGO Careers](https://apify.com/nomad-agent/impactpool-scraper)
- [Devex Jobs Scraper — International Development](https://apify.com/nomad-agent/devex-scraper)

***

**From the maker of [Oink](https://github.com/Exdenta/OinkAIJobSearch)** — an open-source, AI-powered job-search bot for Telegram that runs on these Actors. [Try the free bot](https://t.me/job_search_everyday_bot), get a managed instance at [oinkjobsearch.com](https://oinkjobsearch.com), or browse the [full catalog of 50+ Actors](https://apify.com/nomad-agent).

# Actor input Schema

## `search` (type: `string`):

Free-text query to filter the feed (e.g. <code>software engineer</code>, <code>data</code>, <code>IT digital</code>). Leave empty for all current openings (latest ~20 globally).

## `country` (type: `string`):

Only return postings whose Country field (as published by ReliefWeb) contains this text, e.g. <code>Kenya</code> or <code>Yemen</code>. Case-insensitive, partial match. Leave empty for all countries. Applied after fetching, so it never changes cost.

## `postedSince` (type: `integer`):

Only return postings published within this many days. Set 0 to disable (no freshness filter). Applied after fetching using each posting's publish date, so it never changes cost.

## `maxItems` (type: `integer`):

Maximum number of job openings to return. ReliefWeb's jobs feed always returns roughly the 20 most recent postings per fetch, so values above 20 have no effect. Set 0 for no limit (returns everything the feed provides). Each result returned is billed — see Pricing in the README.

## `enrichOrganisation` (type: `boolean`):

Opt-in: for each posting, follow up to the hiring organisation's ReliefWeb profile page and add its homepage/website (<code>orgWebsite</code>) and description (<code>orgDescription</code>). ReliefWeb's raw jobs feed does not carry these, so this is a billed enrichment add-on. Each organisation is fetched at most once per run. Fields stay <code>null</code> when the source does not expose them.

## `monitoringMode` (type: `boolean`):

Only return postings not seen in prior runs of this Actor (state kept in the Actor's key-value store). Ideal for scheduled runs that should alert on new humanitarian/NGO jobs only. Leave off to return the full current feed every run.

## `resetMonitoringState` (type: `boolean`):

One-shot: clear the remembered set of previously-returned postings before this run, so Monitoring mode treats every current posting as new again. Turn off after the reset run.

## `proxyConfiguration` (type: `object`):

Required: keep the Residential proxy group selected (Apify Residential needs a paid Apify plan, and its bandwidth is billed separately per your plan's proxy rates). ReliefWeb answers datacenter IPs with a holding page instead of the jobs feed — measured 2026-08-01, only 2 of 15 datacenter requests returned real data — so without Residential a run usually comes back empty. Overrides the deprecated <code>Use residential proxy</code> toggle below when set.

## `useResidentialProxy` (type: `boolean`):

Deprecated — use the Proxy configuration field above instead. Kept only for backward compatibility: used as a fallback when Proxy configuration is not set, to decide whether to fetch through an Apify Residential proxy (required because ReliefWeb blocks datacenter IPs).

## `cacheTtlSeconds` (type: `integer`):

Reuse a previously fetched feed for this many seconds instead of fetching again, so repeated runs within the window are faster and skip the network call. Set 0 to always fetch fresh data.

## Actor input object example

```json
{
  "search": "software engineer",
  "country": "Kenya",
  "postedSince": 0,
  "maxItems": 20,
  "enrichOrganisation": false,
  "monitoringMode": false,
  "resetMonitoringState": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "useResidentialProxy": true,
  "cacheTtlSeconds": 1800
}
```

# Actor output Schema

## `dataset` (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("nomad-agent/reliefweb-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("nomad-agent/reliefweb-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).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 nomad-agent/reliefweb-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=nomad-agent/reliefweb-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

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