DEV Community

Cover image for How to Scrape HelloWork Job Offers in France with HelloWork Scraper
ReventaData
ReventaData

Posted on Originally published at apify.com

How to Scrape HelloWork Job Offers in France with HelloWork Scraper

By the end of this tutorial you will have a Python script that pulls French job offers from hellowork.com into structured rows: job title, employer, city, contract type, the published salary, the remote label and the offer link.

HelloWork is a French job board. HelloWork Scraper (reventadata/hellowork-scraper) is the Apify Actor built for this site. You send it a keyword and a few filters, and it returns one row per job offer.

This guide runs it from Python with the Apify API client. The sample rows below come from a real run dated 18 November 2026, with a search for "comptable" (accountant), copied from the run's dataset without edits.


Prerequisites

You need three things:

  1. Python 3 with pip.
  2. A free Apify account, which you can create with an email address or a GitHub login.
  3. Your API token, from Settings > API & Integrations in Apify Console.

Install the client and export the token:

pip install -U "apify-client~=3.0"
export APIFY_API_TOKEN="your_apify_token_here"
Enter fullscreen mode Exit fullscreen mode

No scraping code is needed on your side. The Actor does the fetching.


What you'll achieve

You will search HelloWork for accountant offers and read the rows in Python. The run in this guide asks for ten offers from one result page. The script prints two lines per offer: the title, employer, city and contract on the first line, then the salary, the posting time and the link on the second.

The same script works for a job seeker comparing salaries across cities, a recruiter watching new listings for one role, or an analyst building a table of contract types. Only the input changes. Every example in this guide comes from that one run, so you can check each line against the rows.


Step 1: Open HelloWork Scraper

Open the HelloWork Scraper page on Apify Store. This tutorial uses the API from Python, so the name you need is reventadata/hellowork-scraper.


Step 2: Choose the search

The search is described by a few input fields:

  • searchQueries: a list of job keywords, one search per entry. Empty means no keyword.
  • locations: a list of French cities, one search per entry. Empty means the whole country. A place the site does not know returns no results.
  • contractType: one value from a fixed list, any by default, such as CDI, CDD or Travail_temp (temp work). A value outside the list is refused before the run starts.
  • datePosted: all (default), h (last 24 hours), d (3 days), w (week) or m (month).
  • sortBy: relevance (default) or date for newest first.
  • fetchDetails: off by default. Set it to true to open each offer's page for the full description and exact dates.
  • maxItems: a hard cap on rows across all searches.
  • maxPages: an optional cap on result pages per search, with 30 offers per page.

The run in this guide sets three fields:

{
    "searchQueries": ["comptable"],
    "maxItems": 10,
    "maxPages": 1
}
Enter fullscreen mode Exit fullscreen mode

Keep maxPages small while you test. A search with no keyword and no city covers the whole site.


Step 3: Run it from Python

This script starts the Actor, waits for it, reads the dataset and prints two lines per offer:

import os
from apify_client import ApifyClient

# 1. Initialise the client with your token from the environment
client = ApifyClient(os.environ["APIFY_API_TOKEN"])

# 2. Describe the search: ten accountant offers from one result page
run_input = {
    "searchQueries": ["comptable"],
    "maxItems": 10,
    "maxPages": 1,
}

# 3. Start the Actor and wait for it to finish
run = client.actor("reventadata/hellowork-scraper").call(run_input=run_input)
if run is None or run.status != "SUCCEEDED":
    status = run.status if run else "unknown"
    raise SystemExit(f"Run did not succeed (status: {status}).")

# 4. Read the rows from the run's default dataset
items = client.dataset(run.default_dataset_id).list_items().items
print(f"Retrieved {len(items)} job offers.\n")

# 5. Print two lines per offer: the job, then its salary, posting time and link
for item in items:
    print(f"{item.get('title')} | {item.get('company')} | {item.get('city')} | {item.get('contract')}")
    salary = item.get("salaryText") or "no salary shown"
    print(f"  {salary}, {item.get('postedRelative')}, {item.get('url')}")
Enter fullscreen mode Exit fullscreen mode

The Actor walks results one page at a time, so keep maxPages small while you test.


Step 4: Read the output

Each item in the dataset is one offer. This is the first offer of the run, as the Actor stored it:

{
    "id": "85601956",
    "title": "Comptable Général Comptable H/F",
    "company": "VISIOM",
    "url": "https://www.hellowork.com/fr-fr/emplois/85601956.html",
    "location": "Antony - 92",
    "city": "Antony",
    "department": "92",
    "contract": "CDD",
    "contractTag": null,
    "remote": "Télétravail occasionnel",
    "salaryText": "28 000 - 35 000 € / an",
    "salaryMin": 28000,
    "salaryMax": 35000,
    "salaryCurrency": "EUR",
    "salaryPeriod": "YEAR",
    "postedRelative": "il y a 16 heures",
    "superRecruiter": false,
    "searchUrl": "https://www.hellowork.com/fr-fr/emploi/recherche.html?k=comptable&p=1"
}
Enter fullscreen mode Exit fullscreen mode

A null means the card shows no value for that field.


Understanding your results

Every row carries 18 fields. The ones you will use most:

  • title, company, url: the job title as published, the employer as the card shows it, and the offer link.
  • city and department: split from the card's place, so Antony - 92 gives Antony and 92.
  • contract and contractTag: the contract label, and an extra tag such as 6 mois.
  • remote: the remote-work label, when the card has one.
  • salaryText, salaryMin, salaryMax, salaryCurrency, salaryPeriod: the salary as shown, and split into numbers. salaryPeriod is YEAR, MONTH or HOUR.
  • postedRelative: the posting time as the card words it, such as il y a 2 jours. It is not an exact date.
  • superRecruiter: true when the card carries the Super recruteur badge.

In this run's ten rows, eight offers are CDI and two are CDD. Eight show a salary, and in two salaryText is null. Two rows carry a remote label. Five carry the Super recruteur badge. The Île-de-France row has null in department, and its city holds the region name.


Pro tips

  1. Combine datePosted and sortBy. datePosted: "w" keeps offers from the last week, and sortBy: "date" lists the newest first.
  2. Turn on fetchDetails for exact dates. The card gives only a relative time. With fetchDetails on, each row also carries datePosted, validThrough, the full description, skills and the workplace address. The run is slower.
  3. Keep a keyword or a city in every search. A search with neither covers the whole site, so set maxItems and maxPages before you run one.
  4. Check the salary period before you compare. Salaries come as YEAR, MONTH or HOUR. In this run one offer is monthly (2 208 - 3 000 € / mois, salaryPeriod MONTH) and the rest are yearly.
  5. Read searchUrl when you combine searches. Each row names the search it came from, so a table built from several keywords can group its rows by that field instead of by its position in the dataset.

Troubleshooting

  • Zero rows, status SUCCEEDED. The site answered and no offer matched. The run's status message says so, and the dataset is empty. Check the keyword spelling, and the city name, which must be one the site knows.
  • Zero rows, status FAILED. The input was refused, or the site refused the run. The status message names the cause.
  • Fewer rows than maxItems. Read the run log for Skipped N: reason lines and the closing Pushed N row(s). line, with client.log(run.id).get(). If the run clock ends early, the rows already pushed are kept and the log carries a warning.

Next steps

To repeat a search, save it as an Apify task and attach a schedule, which runs an Actor or task on a cron expression. Datasets export as JSON, CSV, XML, Excel, HTML table, RSS or JSONL (dataset docs).

For current pricing and details, see the Store page.

Check that your use of the data complies with HelloWork's terms of use and with data-protection law.

What are you planning to search for on HelloWork? Drop a comment!

About the author: reventadata builds and publishes data extraction Actors on the Apify Store.

Top comments (0)