ReliefWeb Humanitarian & NGO Jobs Scraper | $3/1k, No API Key
Pricing
from $2.30 / 1,000 job results
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.
Free-text query to filter the feed (e.g. software engineer, data, IT digital). Leave empty for all current openings (latest ~20 globally).
Only return postings whose Country field (as published by ReliefWeb) contains this text, e.g. Kenya or Yemen. Case-insensitive, partial match. Leave empty for all countries. Applied after fetching, so it never changes cost.
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.
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.
Opt-in: for each posting, follow up to the hiring organisation's ReliefWeb profile page and add its homepage/website (orgWebsite) and description (orgDescription). 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 null when the source does not expose them.
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.
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.
Recommended: keep the Residential proxy group selected. ReliefWeb blocks requests from datacenter IPs, so a Residential proxy is needed for the fetch to succeed reliably. Overrides the deprecated Use residential proxy toggle below when set.
{ "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ]}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).