# Devex Jobs Scraper — No API Key Needed (`nomad-agent/devex-jobs-scraper`) Actor

Scrape international-development, NGO, humanitarian and UN jobs from Devex.com — zero setup, no API key: AI extraction is built in. Clean records: title, organisation, location, salary, deadline, URL. Delta mode returns only new postings; alive-check re-verifies known URLs.

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

## Pricing

from $6.00 / 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.

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

## Devex Jobs Scraper — No API Key Needed

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

Scrape **international-development, NGO, humanitarian and UN jobs** from
[Devex.com](https://www.devex.com/jobs) with zero setup. The AI web-search +
extraction step is **built in** — no API key, no configuration, every input
field is optional. Just press Start.

Devex protects every page with bot detection, so classic scrapers get blocked.
This Actor instead discovers postings through AI-driven web search over
Google-indexed metadata and returns clean, structured records.

> 🔑 Prefer to bring your own Anthropic/Mistral key and pay less per result?
> Use the BYOK twin: [nomad-agent/devex-scraper](https://apify.com/nomad-agent/devex-scraper).

### What you get

One dataset record per posting:

| Field | Notes |
|---|---|
| `title`, `company`, `location` | Employer extracted from snippet/URL slug — never a placeholder |
| `url`, `id` | Canonical `www.devex.com/jobs/...` URL + stable job id |
| `postedAt`, `deadline` | `YYYY-MM-DD`, **only when genuinely stated** — never guessed (honest null) |
| `salary`, `contractType`, `workplace` | Only when explicitly stated; null otherwise |
| `employerWebsite`, `snippet` | Org website/profile when visible; one-sentence description |

Devex blocks direct page fetches, so dates/salary come from search metadata and
are often null by design — an honest null beats a fabricated date.

### Modes

- **Discovery (default)** — optional free-text `keyword` and `location`, plus
  structured `contractType` / `workplace` filters. No need to reverse-engineer
  Devex URLs.
- **Delta / monitoring** — turn on `onlyNewSinceLastRun` and schedule the
  Actor: already-delivered postings are skipped and **never billed again**.
  The cheapest way to watch Devex for new vacancies.
- **Alive-check** — paste known Devex job URLs into `jobUrls` to re-verify
  each posting: one row per URL with `isActive` true / false / null.

### Example input

```json
{
  "keyword": "monitoring evaluation",
  "location": "remote",
  "maxItems": 12,
  "onlyNewSinceLastRun": true
}
```

All fields optional — an empty input returns a broad mix of fresh
international-development postings.

### Pricing

Pay per event: a small Actor-start fee plus a fixed price per job returned.
AI usage is included — there is nothing else to configure or pay. Empty runs
push a free explanatory row, and postings skipped by delta mode are never
charged.

### Related Actors

Same buyer, same data shape:
[UNjobs](https://apify.com/nomad-agent/unjobs-scraper) ·
[UN Careers](https://apify.com/nomad-agent/un-careers-scraper) ·
[ReliefWeb](https://apify.com/nomad-agent/reliefweb-scraper) ·
[Impactpool](https://apify.com/nomad-agent/impactpool-scraper) ·
[Researcher bundle](https://apify.com/nomad-agent/researcher-bundle)

### FAQ

**Why is `postedAt` often null?** Devex blocks page fetches; the Actor only
reports a date when the search metadata genuinely states one. It never guesses.

**Is scraping job boards legal?** The Actor only collects publicly visible
posting metadata (no personal data, no login). You are responsible for how you
use the output.

***

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

## `keyword` (type: `string`):

Topic or role keyword to focus the search (e.g. <code>monitoring evaluation</code>, <code>migration</code>, <code>policy analyst</code>). Leave empty to surface a broad mix of international-development postings.

## `location` (type: `string`):

Geographic filter passed to the search (e.g. <code>Geneva</code>, <code>remote</code>, <code>Africa</code>). Leave empty for worldwide listings.

## `contractType` (type: `string`):

Only return postings of this engagement type. Applied by the AI as a search constraint (not a post-hoc regex), so it works on either provider. Leave as <code>Any</code> for all types. Devex is consultancy-heavy, so <code>consultancy</code> is included.

## `workplace` (type: `string`):

Only return postings with this workplace type. Applied by the AI as a search constraint (not a post-hoc regex). Leave as <code>Any</code> for all.

## `onlyNewSinceLastRun` (type: `boolean`):

Delta / monitoring mode: only output postings not delivered on a previous run that also had this flag on. Already-seen postings are dropped before push (never billed), so this is the cheapest way to run this Actor on a schedule and pay only for genuinely new Devex vacancies. State is tracked per Actor in a dedicated key-value store, keyed by each posting's <code>id</code>. The first delta run has nothing to compare against, so it emits everything. See README “Delta mode / monitoring”.

## `jobUrls` (type: `array`):

Alive-check mode (Idealist-style): paste known <code>https://www.devex.com/jobs/...</code> URLs to re-verify whether each posting is still open. When set, the Actor skips keyword/location discovery and instead returns one row per URL with an <code>isActive</code> verdict (true / false / null when it cannot be determined). Leave empty for normal discovery. Note: Devex blocks direct page fetches, so liveness is judged from live web-search signals, not a page load.

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

Maximum number of job postings to return (1–50). Each result is billed under this Actor's pay-per-result pricing; the AI usage behind the run is included — there is nothing else to configure or pay.

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

Reserved for parity / forward-compatibility. Discovery runs server-side inside the AI provider (Claude's built-in web search) or keenable, neither of which routes through an Apify proxy, so this setting is currently inert — there is no direct HTTP fetch to Devex to proxy. Safe to leave at the default.

## Actor input object example

```json
{
  "keyword": "research officer",
  "location": "Geneva",
  "contractType": "",
  "workplace": "",
  "onlyNewSinceLastRun": false,
  "jobUrls": [],
  "maxItems": 12,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# 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 = {
    "jobUrls": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("nomad-agent/devex-jobs-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 = { "jobUrls": [] }

# Run the Actor and wait for it to finish
run = client.actor("nomad-agent/devex-jobs-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 '{
  "jobUrls": []
}' |
apify call nomad-agent/devex-jobs-scraper --silent --output-dataset

```

## MCP server setup

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

```

## OpenAPI specification

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