ReliefWeb Humanitarian & NGO Jobs Scraper | $3/1k, No API Key avatar

ReliefWeb Humanitarian & NGO Jobs Scraper | $3/1k, No API Key

Pricing

from $2.30 / 1,000 job results

Go to Apify Store
ReliefWeb Humanitarian & NGO Jobs Scraper | $3/1k, No API Key

ReliefWeb Humanitarian & NGO Jobs Scraper | $3/1k, No API Key

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.

Pricing

from $2.30 / 1,000 job results

Rating

0.0

(0)

Developer

Nomad Dev

Nomad Dev

Maintained by Community

Actor stats

0

Bookmarked

29

Total users

4

Monthly active users

13 hours ago

Last modified

Categories

Share

ReliefWeb Humanitarian Jobs - Simple

Read stored ReliefWeb humanitarian, NGO and aid-sector job postings with complete original descriptions and application instructions. Each nomad-agent-job-row-v2 posting contains its source ID and URL, title, employer, locations, original description and HTML, posting date, deadline, work arrangement and salary when the source publishes them. Unknown optional facts are null; unavailable locations are an empty array.

This simple tier supports v1 scoring. It has no AI enrichment, translation or custom output. Jobs without a verified complete description are withheld. Runs read the position inventory; they do not fetch ReliefWeb pages or organization profiles.

Input

{
"schemaVersion": "nomad-agent-simple-inventory-search-v1",
"maxItems": 20,
"postedWithin": "any",
"dedupe": {"enabled": true, "key": ""}
}

postedWithin is the only job filter. Use any or a positive duration in hours (h), days (d), weeks (w) or 30-day months (m), up to 36500 days. If the source has no posting date, the first inventory admission date is used; subsequent refreshes do not reset it.

maxItems defaults to 20 and accepts integers from 0 through 200. Zero means 200. A requested maximum is a ceiling; inventory freshness, verified descriptions and repeat suppression can yield fewer rows.

Repeat suppression is enabled by default for the same Apify user, Actor and search. Use a stable dedupe.key for an alert or profile, or disable suppression with {"enabled":false,"key":""}. An unavailable or stale inventory fails the run without a website fallback. Diagnostics and delivery counts are in RUN-SUMMARY, separate from posting rows.

Charges

The existing startup and result prices are unchanged. Startup is charged only after a successful inventory query, including a successful query with no matching rows. An inventory query failure incurs no startup charge. Returned jobs use the existing result event. Full descriptions and application instructions are included; the organization-enrichment event is no longer executed.

Migration from the feed release

This is a versioned input and output migration. Replace older inputs with the example above. search, country, postedSince, enrichOrganisation, proxy settings and cache controls are unsupported and rejected, including an explicitly false enrichment flag. Use postedWithin for posting age. Other filters are outside this simple tier.

The previous feed returned roughly its newest 20 entries; an omitted limit was unbounded within that small feed. The inventory release instead has an explicit default of 20 and a maximum of 200, with zero selecting that maximum. It can return proven stored jobs beyond the old feed window; it does not promise every advertised source job has been collected.

The output preserves complete original text and HTML, all parsed locations, and the stable (source, id) posting key. Titles and employers are not shortened. Location and work arrangement are taken only from explicit source fields. Custom organization fields, inferred coordinates, source diagnostics, warnings and docs are not part of the v2 posting contract. Read RUN-SUMMARY for run diagnostics.