# Teamtailor Job Boards Scraper - All Openings, No Key (`ninhothedev/teamtailor-jobs-scraper`) Actor

$0.35/1K 🔥 Teamtailor Jobs Scraper! Collect open job listings, titles, locations, departments & descriptions from Teamtailor career sites. No key. JSON, CSV, Excel or API in seconds. Feed a job board or recruiting feed ⚡

- **URL**: https://apify.com/ninhothedev/teamtailor-jobs-scraper.md
- **Developed by:** [ninhothedev](https://apify.com/ninhothedev) (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.35 / 1,000 results

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Teamtailor Job Boards Scraper

**The dedicated Teamtailor board reader.** This actor is built specifically for
[Teamtailor](https://www.teamtailor.com/) — one of the most common Applicant
Tracking Systems (ATS) across Europe, used by 13,000+ companies. Give it one or
more company career-site subdomains and it returns **every open role**, with
departments, locations, a remote flag and direct apply URLs. **No API key
required.**

> Using a different ATS? See the sibling actors:
> [Greenhouse](https://apify.com/ninhothedev/greenhouse-jobs-scraper) ·
> [Lever](https://apify.com/ninhothedev/lever-jobs-scraper) ·
> [Ashby](https://apify.com/ninhothedev/ashby-jobs-scraper) ·
> [Workable](https://apify.com/ninhothedev/workable-jobs-scraper).
> This one is the **Teamtailor** specialist.

***

### Why this actor

Teamtailor career sites publish a public **JSON Feed 1.1** document at
`https://{company}.teamtailor.com/jobs.json`. This actor reads that feed
directly — fast, reliable, and no login, token or KYC. Each role is enriched
from the embedded schema.org `JobPosting` block (location, dates, employment
type) so you get clean, structured records ready for a database or spreadsheet.

- **~$0.50 per 1,000 jobs** — cheap enough to poll many companies daily.
- Full HTML **and** clean plain-text descriptions.
- **Location** parsed from structured address data (city, region, country).
- **Remote detection** from the job's location type and description.
- One empty/unknown subdomain only warns; the run continues with the rest.

### Use cases

- **Job aggregators** — ingest openings from hundreds of Teamtailor employers.
- **Recruiting intelligence** — track who is hiring and for what, over time.
- **Hiring signals** — detect team expansion (e.g. a company opening 5 sales roles).
- **Sales prospecting** — reach companies actively hiring for roles you serve.

### How to find a Teamtailor subdomain

1. Open a company's careers page. If the URL is
   `https://{something}.teamtailor.com/...`, the `{something}` is the subdomain.
2. Many companies use a custom domain (e.g. `jobs.company.com`). View the page
   source or network tab — Teamtailor sites reference `*.teamtailor.com` assets
   and expose `.../jobs.json`. Try `https://{guess}.teamtailor.com/jobs.json`
   with common guesses like `career`, `careers`, `join`, or the company name.
3. If `jobs.json` returns a JSON document with an `items` array, you found it.

You enter just the `{name}` part (e.g. `career` for `career.teamtailor.com`). A
full URL is also accepted and normalised automatically.

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `mode` | select | `companies` | Scraping mode. `companies` reads all jobs from each subdomain. |
| `companySubdomains` | array | `["career","doktor","anyfin"]` | Teamtailor subdomains (the `{name}` in `{name}.teamtailor.com`). Prefilled with three verified live sites. |
| `titleFilter` | string | — | Optional case-insensitive substring; only matching titles are kept. |
| `remoteOnly` | boolean | `false` | Keep only roles detected as remote. |
| `maxItemsPerCompany` | integer | `200` | Cap of roles collected per subdomain. |
| `maxItems` | integer | `500` | Total cap across all subdomains (max 5000). |

#### Example input

```json
{
  "mode": "companies",
  "companySubdomains": ["career", "doktor", "anyfin"],
  "titleFilter": "engineer",
  "remoteOnly": false,
  "maxItemsPerCompany": 200,
  "maxItems": 500
}
```

### Output

One dataset item per role:

```json
{
  "type": "job",
  "company": "career",
  "job_id": "3ce2c88b-cbc6-4ae9-8ecb-000466c69037",
  "title": "Group Financial Controller",
  "description": "Join Teamtailor and Help Shape the Future of Work...",
  "description_html": "<h4>Join Teamtailor...</h4>...",
  "tags": [],
  "department": null,
  "location": "Stockholm, Sweden, SE",
  "is_remote": false,
  "date_published": "2026-07-24T13:57:16+02:00",
  "date_modified": null,
  "apply_url": "https://career.teamtailor.com/jobs/8124573-group-financial-controller",
  "authors": [],
  "source": "teamtailor",
  "scraped_at": "2026-08-11T09:00:00+00:00"
}
```

All fields are nullable. `department` and `tags` are populated when a site
exposes them; many Teamtailor feeds omit them, in which case they are `null`/`[]`.

### Notes & limitations

- Reads only the public `jobs.json` feed. The richer JSON:API
  (`/api/v1/jobs`) requires a per-company public API token and is intentionally
  **not** used, so the actor works key-free on any site.
- If **all** subdomains return empty/404, the run fails loudly. A single bad
  subdomain only logs a warning.

### Pricing

Pay-per-result style economics: roughly **$0.50 per 1,000 jobs** scraped.

### Disclaimer

Only publicly available job-posting data is collected. Respect each site's terms
of use and applicable laws when using the output.

# Actor input Schema

## `mode` (type: `string`):

Scraping mode. Currently 'companies' reads all open jobs from the given Teamtailor career-site subdomains.

## `companySubdomains` (type: `array`):

Teamtailor career-site subdomains to scrape. Enter just the '{name}' from {name}.teamtailor.com (a full URL is also accepted). Each site's public jobs.json feed is read. Prefilled with three verified live sites: 'career' (Teamtailor), 'doktor' (Doktor.se), 'anyfin' (Anyfin).

## `titleFilter` (type: `string`):

Optional case-insensitive substring. Only roles whose title contains this text are kept (e.g. 'engineer', 'sjukskoterska'). Leave empty to keep all roles.

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

If enabled, keep only roles detected as remote (remote/anywhere/distributed in title, tags or description, or a TELECOMMUTE job location type).

## `maxItemsPerCompany` (type: `integer`):

Maximum number of roles to collect per subdomain before moving on to the next one.

## `maxItems` (type: `integer`):

Hard cap on total roles across all subdomains. Capped at 5000.

## Actor input object example

```json
{
  "mode": "companies",
  "companySubdomains": [
    "career",
    "doktor",
    "anyfin"
  ],
  "remoteOnly": false,
  "maxItemsPerCompany": 200,
  "maxItems": 500
}
```

# Actor output Schema

## `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 = {
    "companySubdomains": [
        "career",
        "doktor",
        "anyfin"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ninhothedev/teamtailor-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 = { "companySubdomains": [
        "career",
        "doktor",
        "anyfin",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("ninhothedev/teamtailor-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 '{
  "companySubdomains": [
    "career",
    "doktor",
    "anyfin"
  ]
}' |
apify call ninhothedev/teamtailor-jobs-scraper --silent --output-dataset

```

## MCP server setup

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