# Welcome to the Jungle Jobs Scraper (WTTJ) (`djbrooks111/wttj-jobs`) Actor

Scrape Welcome to the Jungle (WTTJ, welcometothejungle.com) jobs into clean rows: contract type, remote policy, key missions and salary as min/max numbers where published, full posting on request. France and Spain checked nightly. $0.50 per 1,000 jobs + $0.001 per run.

- **URL**: https://apify.com/djbrooks111/wttj-jobs.md
- **Developed by:** [David Brooks](https://apify.com/djbrooks111) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 delivered jobs

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## Welcome to the Jungle Jobs Scraper (WTTJ)

Scrape Welcome to the Jungle (WTTJ) jobs into clean rows — key missions and, where published, requirements in the search rows, the full posting body on request — at $0.50 per 1,000 jobs.

Welcome to the Jungle Jobs Scraper extracts WTTJ job listings from welcometothejungle.com into one flat, stable schema. France jobs dominate the index; the default input (English index, no country filter) returns jobs from every office country the board lists, and France and Spain are the markets checked every night. Search by keywords, country, city, contract type, remote policy or publication date. Every row carries the title, the canonical job URL and an apply URL; company, office location, contract type, remote arrangement, profession category, publication date and salary as numbers (minimum, maximum, currency and period) are filled wherever the board publishes them, with a description in HTML and plain text built from the key missions and, where the posting has one, the requirements section the search index publishes. Turn on `includeDescription` and each row also carries the full posting body and, where the board publishes it, the employer's own applicant-tracking apply link.

### What you get

- A description at no extra cost, in HTML and plain text, built from the key missions and the requirements section that ship inside the search result (about 4% of postings publish no requirements section)
- `includeDescription` adds the complete posting body and, where the board publishes one, the employer's applicant-tracking apply URL (otherwise `applyUrl` stays the WTTJ job page) — one extra request per job, still $0.50 per 1,000
- Salary as numbers: `salaryMin`, `salaryMax`, `salaryCurrency` and `salaryPeriod`, left null rather than zeroed when the employer published none
- `workType` normalized across all eleven of the board's contract types, including internships, apprenticeships, freelance and VIE
- `remote` normalized to remote, hybrid or onsite from the board's own fully-remote / partial / occasional / on-site values
- `since` is applied by the search index itself, so a daily monitor never fetches or pays for yesterday's jobs
- Sort by newest first, not just relevance, so incremental runs see new postings at the top
- Stable `sourceId` per job for deduplication across runs, and a `schemaVersion` so keys never change under you

Sample row:

```json
{
  "sourceId": "wttj:979719d5-10f9-4583-80eb-7cc236dc05a7",
  "sourceUrl": "https://www.welcometothejungle.com/en/companies/lucca/jobs/business-developer-existing-business_paris_LUCCA_Gyo6KMp",
  "source": "wttj",
  "title": "Business Developer - Existing Business",
  "company": "Lucca",
  "companyId": "lucca",
  "location": "Paris, Ile-de-France, France",
  "city": "Paris",
  "region": "Ile-de-France",
  "country": "FR",
  "remote": "hybrid",
  "workType": "full-time",
  "category": "Sales & Customer Service",
  "subcategory": "Sales",
  "salaryText": "43,000 EUR - 51,000 EUR per year",
  "salaryMin": 43000,
  "salaryMax": 51000,
  "salaryCurrency": "EUR",
  "salaryPeriod": "year",
  "postedAt": "2026-09-14T13:32:07.000Z"
}
```

### Input

| Field | Description |
|---|---|
| `query` | Keywords, e.g. "data engineer". Leave empty to list everything matching the filters. |
| `locale` | Language index: en, fr, es, cs or sk (default en) |
| `country` | Two-letter country code of the office, e.g. FR, ES, DE |
| `location` | Office city, e.g. "Paris" |
| `contractType` | full_time, part_time, temporary, internship, apprenticeship, freelance, graduate_program, vie, volunteer or other |
| `remote` | fulltime, partial, punctual or no |
| `sortBy` | relevance (default) or date |
| `since` | ISO date; older jobs are filtered out by the index and never charged |
| `includeDescription` | Fetch the full posting body, and the employer's own apply URL where published, per job (slower, same price) |
| `maxItems` | Hard cap on delivered jobs (default 50) |
| `maxCostUsd` | Hard stop on spend, enforced before each request |

### Pricing

Pay per event. You are charged only for delivered, validated results — never for empty pages, blocked requests, or duplicates. `maxCostUsd` is a hard stop enforced before each request.

| Event | Price | Unit |
|---|---|---|
| `run-start` | $0.001 | per run |
| `job` | $0.0005 | per delivered job — $0.50 per 1,000, with or without the full posting body |

- 1,000 jobs with full posting bodies ≈ $0.50, the same price as without them
- A daily 200-job monitor ≈ $3.03/month
- About 2,000 jobs, split into two queries to stay under the index's 1,000-per-query cap ≈ $1.00 plus $0.001 per run

### Why this actor

- Key missions and, on about 96% of postings, the requirements section ship with the search results, so most rows are useful without a second request — and the full posting body costs no more when you do want it
- Reads the board's own public search index and the credentials the site publishes for it, refreshing them at the start of every run so a key rotation does not break your schedule
- Filters run inside the index, not after delivery, so a `since` or country filter reduces what you are charged rather than what you throw away
- Charged only for validated rows. A blocked or empty run bills nothing at all, not even a run-start fee: empty pages, repeated hits and blocked requests never bill you
- `maxItems` and `maxCostUsd` are enforced before the request that would exceed them, so a broad query cannot run away with your credit
- A blocked or changed endpoint fails the run with a typed error instead of quietly finishing with zero rows

### Known limits

- The search index returns at most 1,000 jobs for any single query; the actor stops cleanly there and tells you in the log. Split a broad search by country, city, contract type or `since` to reach the rest
- `location` matches the board's own spelling of the office city, so "Paris" works and "paris, france" does not; `country` is a two-letter ISO code, so "FR" works and "France" is rejected before the run starts
- Listings are multilingual and a French-language posting can appear in the English index; `locale` chooses the index and the URL language, not the posting language
- Salary is published on a minority of listings; `salaryMin`, `salaryMax` and `salaryText` are null on the rest rather than zero
- `expiresAt` is always null — this board does not publish an expiry date
- Without `includeDescription`, `applyUrl` points at the WTTJ job page where the apply button lives; the employer's underlying applicant-tracking URL needs the extra request, and where the board publishes none `applyUrl` stays the WTTJ job page
- The full posting body is not in the search index — about 4% of listings publish no requirements section either, so those rows carry only the key missions until you turn `includeDescription` on
- Employer postings only; no candidate, applicant or recruiter personal data is collected

### Use from an AI agent (MCP)

Add the actor as an MCP tool in Claude Desktop / Cursor via the Apify MCP server:

```json
{ "mcpServers": { "wttj-jobs": { "url": "https://mcp.apify.com?actors=<your-username>/wttj-jobs", "headers": { "Authorization": "Bearer <APIFY_TOKEN>" } } } }
```

The tool accepts exactly the input fields above and returns the same rows.

### Use from n8n / Make

Use the Apify node → "Run actor" with actor `<your-username>/wttj-jobs` and a JSON input such as
`{"query":"data engineer","country":"FR","sortBy":"date","since":"2026-09-01","maxItems":500}` on a daily
schedule, then "Get dataset items".

### FAQ

**Why do I get 1,000 rows when the log says the query matches 90,000?**

The search index refuses to page past 1,000 hits for one query. Slice the search by country, city, contract type or a rolling `since` window and run it several times; each slice gets its own 1,000.

**Do I get the full job description?**

The search result carries the key missions and, on about 96% of postings, the requirements section, and those ship for free. The main posting body is published only on the per-job endpoint, so set `includeDescription` to true for it. That costs one extra request per job but not one extra cent.

**Which countries are covered?**

Whatever the board lists. With no `country` filter a run returns jobs from every office country in the chosen index, and France is the largest by far. France and Spain are the markets the nightly check covers. The actor also accepts the board's Czech and Slovak language indexes (`locale` cs or sk) and any other two-letter office `country`, but those are not part of the nightly check, so treat them as untested.

**Do I need a proxy?**

No. The search endpoint answers from datacenter IPs today. If that changes the run fails with a typed block error and you can enable Apify Proxy in the input.

### Legal and data posture

This actor reads publicly listed job advertisements from Welcome to the Jungle through the public search index the site's own front end uses, with the search credentials the site publishes for that purpose. It never requests the HTML search page that the site's robots.txt disallows, never logs in, never uses accounts or cookies from accounts, and collects no personal data about candidates. Company logos and cover images are deliberately not requested or rehosted. Request rates are modest and 429 responses are honoured with backoff. Data is delivered to you for your own use; we do not build or resell a corpus.

### Support

Open an issue on the Issues tab; first response within 6 hours on business days. Every run writes a `RUN_SUMMARY` record to the key-value store with items delivered, events charged, and the stop reason.

# Actor input Schema

## `query` (type: `string`):

Search keywords, e.g. "data engineer". Leave empty to list everything matching the filters below.

## `locale` (type: `string`):

Which language index to search. Listings are multilingual; the index affects matching and the job URL, not which companies are covered.

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

Two-letter ISO country code of the office, e.g. FR, ES, DE.

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

Office city, exactly as Welcome to the Jungle spells it, e.g. "Paris" or "Lyon".

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

Restrict to one contract type.

## `remote` (type: `string`):

Restrict to one remote arrangement.

## `sortBy` (type: `string`):

Order of the search results: Welcome to the Jungle's relevance ranking, or newest postings first.

## `since` (type: `string`):

ISO date (2026-09-01) or datetime (2026-09-01T06:00:00Z); a value with no offset is read as UTC. Applied by the search index, so older jobs are never fetched or charged.

## `includeDescription` (type: `boolean`):

Fetch the complete posting body and the employer's apply URL for each job (one extra request per job; slower, same price). Without it every row still carries the key missions and requirements section.

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

Hard cap on delivered jobs for this run. Default 50 keeps free trials cheap; raise it for production.

## `maxCostUsd` (type: `number`):

Hard stop: the run never charges more than this. Enforced before each request, not after.

## `stateNamespace` (type: `string`):

Optional suffix for this actor's cross-run state store, so separate schedules or test runs keep separate monitor baselines and watermarks (e.g. `prod`, `staging`).

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

No proxy is needed for this search API today. Enable one only if you see blocks.

## `outputFormat` (type: `string`):

flat (default): one level of keys, spreadsheet-friendly. nested: keep objects.

## Actor input object example

```json
{
  "query": "developer",
  "locale": "en",
  "sortBy": "relevance",
  "includeDescription": false,
  "maxItems": 50,
  "maxCostUsd": 5,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "outputFormat": "flat"
}
```

# Actor output Schema

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

Every delivered row, validated against the actor's entity schema (flat keys, ISO dates, sourceUrl, scrapedAt, sourceId). Only delivered rows are billed.

## `runSummary` (type: `string`):

RUN_SUMMARY: items delivered, events charged, USD charged, blocks met, requests made, the typed error if the run failed, and actor-specific meta.

# 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 = {
    "query": "developer",
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("djbrooks111/wttj-jobs").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 = {
    "query": "developer",
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("djbrooks111/wttj-jobs").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 '{
  "query": "developer",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call djbrooks111/wttj-jobs --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,djbrooks111/wttj-jobs"
        }
    }
}
```

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/McSxyIT4vOElT43Zc/builds/pNMrkxIJDi7R1RJ74/openapi.json