Hellowork Search Scraper avatar

Hellowork Search Scraper

Pricing

from $2.99 / 1,000 hellowork job records

Go to Apify Store
Hellowork Search Scraper

Hellowork Search Scraper

Scrape job listings from Hellowork.com (formerly RegionJobs), a major French job board. Extract job titles, companies, locations, salary ranges, contract types and descriptions for French recruitment.

Pricing

from $2.99 / 1,000 hellowork job records

Rating

0.0

(0)

Developer

Jobs API

Jobs API

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a month ago

Last modified

Share

Hellowork France Jobs Scraper

Extract public jobs from Hellowork by keyword and optional French location. The Actor uses lightweight HTTP requests, stable offer IDs, verified p pagination, deduplication, bounded detail concurrency, and JobPosting JSON-LD enrichment.

Input

  • query: required job keywords.
  • location: optional city or region.
  • maxItems: 1-500 unique jobs.
  • maxPages: 1-20 result pages.
  • includeDetails: enrich listings from canonical job pages.
  • maxDetailItems: 0-100 detail requests.
  • maxConcurrency: 1-10 concurrent detail requests.
  • maxRetries: 0-4 transient retries. Source denials (401/403/429/451) and visible challenges are never retried.
  • requestTimeoutSecs: 10-120 seconds per request.
  • proxyConfiguration: optional Apify/custom proxy; direct access is the default.
{"query":"developpeur","location":"Paris","maxItems":10,"maxPages":2,"includeDetails":true,"maxDetailItems":10,"proxyConfiguration":{"useApifyProxy":false}}

Output

Dataset rows contain the stable offer ID, title, employer, location, contract and salary fields, canonical URL, and search/page provenance. Verified detail pages can add full description HTML/text, structured sections, responsibilities, requirements, benefits, skills, education/experience, dates, workplace type, and application target. Listing rows are retained if an individual detail request fails; empty optional values are omitted.

Every row states whether detail was fetched and verified, the listing/detail HTTP statuses, execution environment, proxy use, and timestamp. OUTPUT.status is the Apify process state (SUCCEEDED or FAILED); OUTPUT.resultStatus is the data outcome (COMPLETE, LIMITED, SKIPPED, DEFERRED, NO_DATA, or FAILED). An empty or unrecognized parse is SUCCEEDED/DEFERRED; this Actor reports NO_DATA only after affirmative source-authored empty-result evidence is recognized. A confirmed access boundary on an official HTTPS Hellowork URL stops new detail scheduling, aborts in-flight detail requests, discards staged job rows, and is SUCCEEDED/SKIPPED only if its summary is persisted. Off-origin denials and unverified access signals are DEFERRED, not blocked. Generic request/controller/network failures with no stored rows are SUCCEEDED/DEFERRED; non-block failures after rows are stored preserve those rows as SUCCEEDED/LIMITED. Only complete, provenance-backed job rows are written to the Dataset; diagnostics remain in the OUTPUT key-value summary. Fatal zero-row errors write the summary where possible, then fail the Actor run.

Run npm test and npm run check for source-independent checks. npm run validate inspects local dataset rows and intentionally fails if there are none; unit tests do not require a source request or generated storage.

Use public data responsibly and follow Hellowork terms and applicable laws. The Actor does not access authenticated or private applicant data.