# France Jobs Scraper · 8 Boards, One Schema (`bibian/france-jobs-scraper`) Actor

Extract job postings from 8 major French job boards in one run: Free-Work, Welcome to the Jungle, HelloWork, Meteojob, France Travail, Emploi Territorial, Choisir le Service Public and Qapa. One unified schema, deduplicated across sources, no login.

- **URL**: https://apify.com/bibian/france-jobs-scraper.md
- **Developed by:** [Vivien MORVAN](https://apify.com/bibian) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 job postings

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

## France Jobs Scraper · 8 Boards, One Schema

Extract job postings from 8 major French job boards in a single run — [Free-Work](https://www.free-work.com), [Welcome to the Jungle](https://www.welcometothejungle.com), [HelloWork](https://www.hellowork.com), [Meteojob](https://www.meteojob.com), [France Travail](https://candidat.francetravail.fr), [Emploi Territorial](https://www.emploi-territorial.fr), [Choisir le Service Public](https://choisirleservicepublic.gouv.fr) and [Qapa](https://jobs.qapa.fr) — mapped to one unified schema, deduplicated across sources. No login, no browser to configure.

### What you can do with it

- **Search French jobs across the private sector, tech, retail, temp staffing and the public sector in one run**, instead of buying and maintaining 8 separate scrapers.
- **Filter once, everywhere**: `keywords`, `location`, `remote` and `publishedWithinDays` apply the same way across all 8 sources.
- **Compare pay and location across boards**: every record shares the same `salaryMin`/`salaryMax`, `city` and `employmentType` fields, whichever site it came from.
- **Monitor new postings daily**: schedule it with `onlyNew` checked and `publishedWithinDays: 1` to get, and pay for, only what is new since the last run.

### Input

| Field | What it does |
|---|---|
| `keywords` | Job title, skill or trade, for example `développeur` or `infirmier`. Empty means every posting. |
| `location` | City, department or region, for example `Lyon` or `Bretagne`. Empty means all of France. |
| `sources` | Which of the 8 job boards to query in this run. Defaults to all 8. |
| `publishedWithinDays` | Keep only postings published in the last N days. Use `1` for a daily monitoring run. |
| `remote` | Keep only postings with this remote policy: `any`, `remote`, `hybrid` or `onsite`. |
| `maxItems` | The run stops once this many postings are saved, across all sources combined (default 200). |
| `includeDescriptions` | Add the job description as plain text (default on). |
| `onlyNew` | For scheduled runs: skip postings an earlier run of this same search already delivered. |

### Output

One record per posting, in the schema shared by every job actor on this account:

| Field | Type | Meaning |
|---|---|---|
| `id` | string | Stable identifier (`<source>:<native id>`), used to deduplicate between runs. |
| `url` | string | Public page of the posting. |
| `title` | string | Job title as published. |
| `companyName` | string or null | Employer name; `null` when hidden (then `confidentialCompany: true`). |
| `companyUrl` | string or null | Company page on the source site, when it exists. |
| `locationLabel` | string or null | Location as displayed by the site. |
| `city` | string or null | City. |
| `region` | string or null | Region, department or equivalent. |
| `postalCode` | string or null | Postal code. |
| `country` | string | ISO 3166-1 alpha-2 country code (`FR`). |
| `remote` | string | `remote`, `hybrid`, `onsite` or `unknown`. |
| `employmentType` | string | `full_time`, `part_time`, `contract`, `freelance`, `internship`, `apprenticeship`, `temporary` or `unknown`. |
| `salaryMin` / `salaryMax` | number or null | Salary range, as numbers. |
| `salaryCurrency` | string or null | ISO 4217 currency code. |
| `salaryPeriod` | string or null | `hour`, `day`, `month` or `year`. |
| `datePosted` | string or null | Publication date, ISO 8601. |
| `validThrough` | string or null | Expiry date, ISO 8601. |
| `description` | string or null | Plain-text description, only when `includeDescriptions` is on. No personal data. |
| `experienceLevel` | string or null | As named by the site. |
| `industry` | string or null | As named by the site. |
| `skills` | string\[] | Skills listed by the site, if any. |
| `source` | string | Host name of the source site. |
| `sourceId` | string | Native identifier on the source site. |
| `scrapedAt` | string | Extraction timestamp, ISO 8601. |

Site-specific fields are kept in addition to these (never in place of them) — for example Qapa's `trade` and mission `startDate`/`endDate`, or Choisir le Service Public's `employmentTypeLabel`.

### Why this one

8 boards in one run, one schema. `source` on every row to filter or split by board. Deduplicated between sources, by URL and by (title, company, city). No connection, no login, no browser to configure.

### Good to know

- `employmentType` and `remote` are read from each site's own fields when it has one; when a source carries no such field (most public-sector and staffing boards), they are inferred from the title and description, and left `unknown` rather than guessed when nothing matches.
- Every result is deduplicated across all 8 sources before it is counted or charged.
- No personal data: contact details of individuals are stripped from descriptions; only companies and public employers are named.

# Actor input Schema

## `keywords` (type: `string`):

Job title, skill or trade, for example "développeur" or "infirmier". Leave empty to get every posting.

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

City, department or region, for example "Lyon" or "Bretagne". Leave empty for all of France.

## `sources` (type: `array`):

Job boards to query in this run.

## `publishedWithinDays` (type: `integer`):

Keep only postings published in the last N days. Use 1 for a daily monitoring run. Leave empty for no limit.

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

Keep only postings with this remote policy.

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

The run stops once this many postings are saved, across all sources combined.

## `includeDescriptions` (type: `boolean`):

Add the job description as plain text.

## `onlyNew` (type: `boolean`):

For scheduled runs. Skip the results that an earlier run of this same search already delivered, so each run returns, and charges, only what is new. The memory is kept in the key-value store "only-new-memory-bibian" of your account.

## Actor input object example

```json
{
  "keywords": "développeur",
  "sources": [
    "free-work",
    "welcometothejungle",
    "hellowork",
    "meteojob",
    "francetravail",
    "emploi-territorial",
    "choisirleservicepublic",
    "qapa"
  ],
  "remote": "any",
  "maxItems": 100,
  "includeDescriptions": true,
  "onlyNew": false
}
```

# Actor output Schema

## `postings` (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 = {
    "keywords": "développeur",
    "location": "",
    "maxItems": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("bibian/france-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 = {
    "keywords": "développeur",
    "location": "",
    "maxItems": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("bibian/france-jobs-scraper").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 '{
  "keywords": "développeur",
  "location": "",
  "maxItems": 100
}' |
apify call bibian/france-jobs-scraper --silent --output-dataset

```

## MCP server setup

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

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/M0rd02aH3exKWhR65/builds/si9s3xFUUiX9K0zp7/openapi.json