Recruitee Job Scraper — Careers API

For European talent teams, job aggregators, and HR analytics platforms that need clean job data from Recruitee-powered companies — with salary ranges when published.

Pay per result — $1.50 / 1,000 jobs. No API key. No login. No proxy required. Runs in Apify cloud.

Scrape job postings from any Recruitee-powered company careers page via the official public API. Give it a list of company slugs — get back clean, enriched job data in seconds. No login, no API key, no browser, no proxy required.

Get started instantly: use the pre-filled example (bunq, personio) or swap in any Recruitee company slug. Try it free — Apify's $5/month free tier covers thousands of jobs.

What this Recruitee scraper does

• Fetches every open job from any company that uses Recruitee ATS, using the official <slug>.recruitee.com/api/offers/ endpoint.
• Returns a clean flat schema — identical fields every run, no parsing surprises.
• Enriches each job with seniority (intern / entry / mid / senior / lead / staff / principal / manager / director / vp / executive) — using Recruitee's native experience_code first, falling back to title-regex inference.
• Detects remote type (remote / hybrid / onsite) from Recruitee's explicit boolean flags — far more reliable than text parsing.
• Returns salary when the company publishes it (formatted as a range string).
• Returns full job descriptions as both plain text and HTML (togglable).
• Includes a parse_confidence score (0–1.0) and warnings list in every record — you see exactly how clean the data is.
• Supports multi-company batch runs (scrape many companies in one run).
• Filters by title keyword, location keyword, or remote-only.
• maxJobsPerCompany cap (default 50) prevents surprise bills on first runs.

How to find a Recruitee slug

The slug is the subdomain of the company's Recruitee careers page:

• bunq.recruitee.com → slug is bunq
• personio.recruitee.com → slug is personio
• tidio.recruitee.com → slug is tidio

Many EU-based tech companies use Recruitee: bunq, Personio, Bynder, Teamwork, Recruitee itself, and hundreds more.

What data you get

One flat row per job — 18 structured fields:

{
  "title": "AML Branch Manager, Romania",
  "company": "bunq",
  "location": "Bucharest, București, Romania",
  "remote_type": "hybrid",
  "seniority": "senior",
  "salary": null,
  "department": "Support & Operations",
  "employment_type": "fulltime_permanent",
  "posted_at": "2026-05-29T09:45:21+00:00",
  "url": "https://careers.bunq.com/o/aml-branch-manager-romania",
  "apply_url": "https://careers.bunq.com/o/aml-branch-manager-romania/c/new",
  "job_id": "2620732",
  "global_id": "recruitee:bunq:2620732",
  "description_text": "At bunq, we are more than just a bank...",
  "description_html": "<p>At bunq, we are more than just a bank...</p>",
  "parse_confidence": 1.0,
  "warnings": [],
  "scraped_at": "2026-05-31T12:00:00+00:00"
}

Field notes:

• remote_type uses Recruitee's explicit remote, hybrid, on_site boolean flags — not fragile text parsing. Values: remote, hybrid, onsite, or null.
• seniority uses Recruitee's experience_code field when available (more accurate than title inference). Falls back to regex on the title.
• salary is null if the company doesn't publish it. When published, it is formatted as a human-readable string (e.g. "120000–150000 USD /year").
• parse_confidence is 1.0 for a fully-populated job; small deductions for missing optional fields. Check warnings for the reason codes.
• global_id format: recruitee:{slug}:{job_id} — stable identifier for deduplication across runs.

Input schema

Field	Type	Default	Description
companies	string array	[bunq, personio]	Recruitee company slugs to scrape
titleKeyword	string	—	Case-insensitive title filter
locationKeyword	string	—	Case-insensitive location filter
remoteOnly	boolean	false	Return only remote jobs
maxJobsPerCompany	integer	50	Cap per company (0 = unlimited)
includeDescriptions	boolean	true	Include description_text + description_html

Pricing

Pay-per-result: $1.50 / 1,000 jobs ($0.0015 each). You pay only for jobs returned.

Worked example: 3 companies × 50 jobs = 150 results = $0.23. 10 companies × 100 jobs = 1,000 results = $1.50.

FAQ

Do I need an API key or proxy? No. Recruitee's careers API (<slug>.recruitee.com/api/offers/) is publicly accessible — no auth, no proxy required.

What output formats are available? JSON, JSONL, CSV, and Excel via the Apify dataset export, plus the Apify REST API.

Can I schedule daily runs? Yes — use Apify Scheduler. Use global_id (recruitee:<slug>:<job_id>) as a stable dedup key across runs.

What if salary is null for most jobs? Most Recruitee companies don't publish compensation publicly. The salary field is null when absent — honest and machine-readable. When published, you get a full range string (e.g. "120000–150000 USD /year").

Reliability

The Recruitee careers API is a stable, publicly accessible endpoint with no authentication, no rate limiting, and no HTML parsing. This actor uses zero browser, zero proxy — just direct HTTP to an official JSON API. Parse confidence is consistently 1.0 on well-populated boards.

Typical run: 30–100 jobs for one company in under 3 seconds.

Use cases

• Job aggregation — build a searchable careers board for European tech companies.
• Hiring intelligence — track headcount growth, new departments, role types.
• AI agent input — feed job data to an LLM agent for matching, summarizing or alerting.
• Lead generation — identify companies actively hiring in specific functions.
• Competitive analysis — monitor competitor hiring signals in real time.

Alternatives and comparison

The most comprehensive scraper for Recruitee-powered job boards — heavily used by European tech companies: bunq, Personio, Bynder, Teamwork, Tidio, and hundreds more.

Feature	This scraper	Typical ATS scrapers
Salary field (when published)	Yes	Rarely
Native remote/hybrid/onsite flags	Yes	No (text parsing only)
parse_confidence score	Yes	No
Seniority (native experience_code + title fallback)	Yes	No
EU-focused company support	Yes	Partial
Multi-company batch	Yes	Some
global_id for dedup	Yes	No
Price	$1.50/1k	varies

Salary honesty: salary is null when the company doesn't publish it. When it IS published, you get the full range string (e.g. "120000–150000 USD /year") — machine-readable and ready for filtering.

parse_confidence (0.0–1.0) and warnings in every record — deductions for missing job_id (0.15), title (0.15), url (0.10), posted_at (0.05), description (0.05).

If your target companies use Personio instead of Recruitee, see our Personio Job Scraper.

Use with AI agents (MCP)

This actor is MCP-compatible. Use it as a data source in n8n, Make, or any LLM agent pipeline.

https://mcp.apify.com/?tools=bovi/recruitee-job-scraper

The flat schema with global_id (recruitee:<slug>:<job_id>) and native salary ranges is drop-in-ready for vector databases, EU job-matching LLMs, and automated sourcing workflows. Need Greenhouse, Lever, Ashby, SmartRecruiters and Personio in the same pipeline? Use the flagship Multi-ATS Job Scraper — 6 ATS, one unified schema.

Integrations

Built for European talent teams and job aggregators tracking open roles at Recruitee-powered companies — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

Not affiliated with Recruitee

This actor uses the public Recruitee careers API, which is freely accessible to anyone. It is not affiliated with, endorsed by, or partnered with Recruitee or its parent company Recruit Holdings.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.