# Recruitee Jobs Scraper — Recruitee Careers Pages (Tellent) (`northbell/recruitee-jobs-scraper`) Actor

Recruitee jobs scraper: every open role on any company's Recruitee careers site — title, department, location, remote/hybrid, employment type, salary when published, posting date, full description — plus a hiring tracker: exactly which roles are new or closed since your last run.

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

## Pricing

from $0.40 / 1,000 jobs

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

## Recruitee Jobs Scraper

**Know every week which roles your target companies opened and closed** — without checking their careers pages. Put in the companies, schedule it, and get only the new roles (plus closed ones and a per-company count) from any company's public **Recruitee** job board. Exact, not sampled: the official public API returns every open role at once. No login, no cookies, no proxies.

> **Don't know which companies to watch?** The [Greenhouse Jobs Scraper](https://apify.com/northbell/greenhouse-jobs-scraper) searches **4,800 companies by job title** — no company names needed — and reports exactly which matching roles are new or closed each run.

### Why the "new / closed" is exact here

Most job scrapers search a job site and get back a *sample*: run the same search twice and a different slice comes back, so "new since yesterday" is partly noise. A Recruitee board is different — the company's public API returns **every open role at once**. So this Actor keeps the list of role IDs from your last run and compares: a role that appears is new, a role that disappears has closed. No estimation.

bunq's open roles came back in half a second.

### What you get

| Field | |
|---|---|
| `title`, `department`, `team` | as the company wrote them |
| `location`, `locations` | the main location and every secondary one |
| `remote`, `workplaceType`, `employmentType` | when the board provides them — otherwise `null`, not a guess |
| `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryInterval` | Recruitee has salary fields (min, max, currency, period); filled in when the company publishes them, otherwise null. |
| `postedAt` | the real publish date from the board |
| `isNewSinceLastRun` | `true` / `false`, or `null` on the first run (unknown, not "old") |
| `description` | full text, HTML stripped (turn off with *Include the full description*) |
| `jobUrl`, `applyUrl` | links straight to the posting |

Closed roles come back as their own rows (`type: "closed"`) with the title and when they were last seen. Each company also gets one free summary row (`type: "company"`) with `openRoles`, `newRoles`, `closedRoles` and `netChange` — the hiring signal without counting rows yourself.

### Input

Put the company's board name or careers-page URL in **Companies** — for example `bunq` or `bunq.recruitee.com`. Many companies in one run is fine and cheaper than one run each.

Optional filters (title, location, remote only, published salary only) narrow what you get back. They **do not** change the new/closed comparison, which always uses the full board — so changing a filter never makes roles look "closed".

A company that is not on Recruitee, or has no public board, comes back as an `error` row and the run carries on.

### Example output

One real row from a test run (long text shortened here with …):

```json
{
  "type": "job",
  "provider": "recruitee",
  "board": "bunq",
  "companyName": "bunq",
  "team": null,
  "updatedAt": null,
  "description": "As a Cards Experience Guide, you'll be the person who gives our users peace of mind every time they pay with their bunq card. Whether they need a refund, have a…",
  "salaryMin": null,
  "salaryMax": null,
  "salaryCurrency": null,
  "salaryInterval": null,
  "salaryText": null,
  "jobId": "2768887",
  "title": "Cards Experience Guide",
  "department": "Support & Operations",
  "location": "Amsterdam, Netherlands",
  "locations": [
    "Amsterdam, Netherlands",
    "İstanbul, Türkiye",
    "Sofia, Bulgaria"
  ],
  "workplaceType": "hybrid",
  "remote": false,
  "employmentType": "fulltime_permanent",
  "postedAt": "2026-10-02T13:38:06.000Z",
  "jobUrl": "https://careers.bunq.com/o/cards-experience-guide-2",
  "applyUrl": "https://careers.bunq.com/o/cards-experience-guide-2/c/new",
  "company": "bunq",
  "isNewSinceLastRun": false
}
```

### Get only the new roles every morning (3 steps)

1. Open this Actor in Apify Console, fill in your input, set **What to return** to **Only … new since the last run**, and click **Save as a new task**.
2. On the task, add a **Schedule** — daily at 07:00, or weekly on Monday.
3. Open the task's **Integrations** tab and connect **Slack**, **email**, **Google Sheets** (or Zapier / Make / a webhook). Each run then delivers only what is new.

You pay only for the new rows plus $0.01 per run, so a quiet day costs about a cent.

### Pricing

Pay per role returned — **$0.50 per 1,000 roles**, plus $0.01 per run. Closed-role rows and errors are free.

### For AI agents

Call with `{"companies": ["bunq"]}`. Each row has `type`: `job`, `closed` or `error`. `isNewSinceLastRun: null` means "no previous run to compare with", not "old".

**Filters on every run (10/2026):** posted within the last N days, experience level (read from the title: intern → executive, also returned as a `seniority` column) and employment type. They only narrow what is returned — no extra requests, no extra cost.

**Same core columns on every northbell job scraper** (10 company-career-page scrapers + 15 job sites), so you can stack them into one table: `jobId`, `title`, `company`, `location`, `remote` (true / false / null), `employmentType`, `postedAt`, `jobUrl`, `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryInterval`, `isNewSinceLastRun`. Unknown is `null`, never a guess.

### Sister Actors

[Greenhouse Jobs Scraper](https://apify.com/northbell/greenhouse-jobs-scraper) · [Lever Jobs Scraper](https://apify.com/northbell/lever-jobs-scraper) · [Ashby Jobs Scraper](https://apify.com/northbell/ashby-jobs-scraper) · [Workday Jobs Scraper](https://apify.com/northbell/workday-jobs-scraper) · [Workable Jobs Scraper](https://apify.com/northbell/workable-jobs-scraper) · [SmartRecruiters Jobs Scraper](https://apify.com/northbell/smartrecruiters-jobs-scraper) · [Recruitee Jobs Scraper](https://apify.com/northbell/recruitee-jobs-scraper) · [Personio Jobs Scraper](https://apify.com/northbell/personio-jobs-scraper) · [Breezy HR Jobs Scraper](https://apify.com/northbell/breezy-hr-jobs-scraper) — same fields, same exact change tracking, one per job-board provider.

For LinkedIn: [LinkedIn Company Jobs Scraper](https://apify.com/northbell/linkedin-company-jobs-scraper) · [Free LinkedIn Job Details from URL](https://apify.com/northbell/linkedin-job-detail-scraper).

# Actor input Schema

## `companies` (type: `array`):

The company's Recruitee board name or careers-page URL (bunq.recruitee.com). One per line. Add as many as you like — one run, one start fee.

## `titleKeywords` (type: `string`):

Comma-separated. Keep roles whose title contains any of these, e.g. "engineer, data".

## `locationKeywords` (type: `string`):

Comma-separated. Matched against every location of the role, e.g. "london, remote".

## `remoteOnly` (type: `boolean`):

Keep only roles the board marks as remote.

## `postedWithinDays` (type: `integer`):

Keep only roles first published in the last N days. Roles with no publish date are left out when you set this, and counted in OUTPUT.

## `experienceLevels` (type: `array`):

Keep only these levels, read from the job title (the same words on every northbell job scraper; each row also gets a seniority column). Product, account and other non-people "managers" count as mid level.

## `employmentTypes` (type: `array`):

From the board's own employment type (Lever and Ashby state it; Greenhouse rarely does), else from the title. Roles whose type is not stated are left out when you set this, and counted in OUTPUT.

## `withSalaryOnly` (type: `boolean`):

Keep only roles where the company published a pay range.

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

Plain text. Turn off for smaller, faster output.

## `output` (type: `string`):

Schedule this Actor weekly or daily and pick "Only new" to pay only for new roles. The first run returns everything (there is nothing to compare with yet). Closed roles and the per-company summary rows are always free.

## `trackChanges` (type: `boolean`):

The board returns every open role at once, so the difference from your previous run is exact — not a sample. First run marks everything as unknown (null).

## `maxJobsPerCompany` (type: `integer`):

Stops returning roles from one company after this many. The new/closed comparison still uses the whole board.

## Actor input object example

```json
{
  "companies": [
    "bunq"
  ],
  "remoteOnly": false,
  "withSalaryOnly": false,
  "includeDescription": true,
  "output": "all",
  "trackChanges": true,
  "maxJobsPerCompany": 1000
}
```

# Actor output Schema

## `all` (type: `string`):

No description

## `jobs` (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 = {
    "companies": [
        "bunq"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("northbell/recruitee-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 = { "companies": ["bunq"] }

# Run the Actor and wait for it to finish
run = client.actor("northbell/recruitee-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 '{
  "companies": [
    "bunq"
  ]
}' |
apify call northbell/recruitee-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,northbell/recruitee-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/MtQAhZxLGgeU8dO0O/builds/wiSHBLDAoIjpkdfHE/openapi.json