# Job Scraper - Job Board API: LinkedIn Jobs, Arbeitnow, Remotive (`thebee/jobboardscraper`) Actor

Multi source job API and job feed aggregator. LinkedIn public guest feed, Arbeitnow, Remotive and Himalayas in one call. Job listings API, no API keys or login, no browser. Output normalised and de-duplicated across sources. Pay per job result.

- **URL**: https://apify.com/thebee/jobboardscraper.md
- **Developed by:** [ttgi](https://apify.com/thebee) (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 $5.00 / 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.

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

## Job Board Scraper

Four job sources in one call. No API keys, no login, no browser.

### Sources

| Source | Notes |
|---|---|
| LinkedIn | public guest job-card feed, paginated, ~10/page |
| Arbeitnow | ~325 listings per call |
| Remotive | remote-only, searchable |
| Himalayas | remote-only |

### Input

```json
{ "keyword": "python developer", "location": "Remote", "limit": 50 }
```

### Output

Normalised and de-duplicated across sources:

```json
{
  "title": "...", "company": "...", "location": "...", "remote": true,
  "postedAt": "2026-09-28", "url": "...", "description": "...",
  "source": "linkedin-public-guest"
}
```

### Pricing

Two ways to pay. Pick whichever fits how you use it.

**Pay per result — $0.005 per job row.** No commitment. Every row this actor
returns is charged at $0.005; compute is billed separately at cost (near zero —
no headless browser). A 200-job run is about $1.00.

**Monthly pass — $15 for 30 days.** You are charged per *job row returned*, not
per run. The pass is cheaper once you pull more than **3,000 job rows a month**
(3,000 x $0.005 = $15 — above that, the flat $15 wins). Buy it by adding the
opt-in flag to your run input:

```json
{ "keyword": "python developer", "monthlyPass": true, "limit": 500 }
```

While `monthlyPass` is `true`, **no per-result charge is applied** — the $15
already covers every run in the 30-day window, however many rows it returns.
Set it back to `false` (or omit it) to return to per-result billing.

The pass is **not** automatically renewed: it covers exactly 30 days from the
run that activates it, and nothing is charged unless you run with
`monthlyPass: true` again. Renewing early simply activates a new 30-day window
from that run, so you are never charged twice for the same day.

### Why it is cheap to run

Every source is server-rendered JSON or HTML. No headless browser, so compute
cost per run is near zero and the margin on pay-per-event pricing is ~98%.

# Actor input Schema

## `keyword` (type: `string`):

Job title or keyword to search for, e.g. 'python developer'.

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

Location filter for sources that support one.

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

Which sources to query. Defaults to all available.

## `limit` (type: `integer`):

Upper bound per source before de-duplication.

## `monthlyPass` (type: `boolean`):

Optional 30-day pass, charged once per opted-in run at $15. While true, no per-result charge is applied - the pass covers every run in the 30-day window, however many rows it returns. Cheaper than per-result billing above 3,000 job rows per month. It does NOT auto-renew: set it back to false (or omit it) to return to per-result billing, and pass true again to start a new window.

## Actor input object example

```json
{
  "keyword": "software engineer",
  "location": "Remote",
  "sources": [
    "linkedin",
    "arbeitnow",
    "remotive",
    "himalayas"
  ],
  "limit": 50,
  "monthlyPass": false
}
```

# Actor output Schema

## `id` (type: `string`):

No description

## `title` (type: `string`):

No description

## `company` (type: `string`):

Parsed from the posting URL slug; may be null.

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

No description

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

No description

## `postedAt` (type: `string`):

YYYY-MM-DD, or null if the source omits it.

## `url` (type: `string`):

No description

## `salary` (type: `string`):

Raw salary string as posted. Only some sources provide it.

## `description` (type: `string`):

Plain-text excerpt, up to 600 characters.

## `tags` (type: `string`):

No description

## `source` (type: `string`):

No description

## `scrapedAt` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("thebee/jobboardscraper").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("thebee/jobboardscraper").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 '{}' |
apify call thebee/jobboardscraper --silent --output-dataset

```

## MCP server setup

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

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/TmWijFEWx3PYAvKYK/builds/mvS5cMR1668m00icJ/openapi.json