# Teamtailor Scraper \[Only $1/1K💰] | Jobs | ATS Careers Data (`ahmed_jasarevic/jobs-teamtailor-scraper`) Actor

Extract job postings from any Teamtailor career site — Polestar, Savills, Huel and thousands more. Get titles, full descriptions, locations, dates and company data as structured JSON for job boards, hiring-signal monitoring and EU recruitment research. No API key, no login.

- **URL**: https://apify.com/ahmed_jasarevic/jobs-teamtailor-scraper.md
- **Developed by:** [Ahmed Jasarevic](https://apify.com/ahmed_jasarevic) (community)
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.90 / 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.
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

## Teamtailor Scraper

Teamtailor Scraper extracts job postings from any Teamtailor career site — the applicant tracking system used by thousands of employers, from Polestar and Oatly to Doctors Without Borders, Arsenal FC and Huawei. It reads the keyless public `jobs.json` feed that every Teamtailor career site exposes and returns structured rows — title, URL, publish date, full HTML description, locations and the raw schema.org `JobPosting` — with no API key, no login and no browser.

Built for job boards, ATS aggregators, HR-tech teams, recruitment agencies and hiring-data analytics.

### Monitor Teamtailor Career Sites and Build Job Databases

- **Job posting monitoring and hiring-signal tracking** — schedule daily runs to detect new openings at specific Teamtailor employers (e.g. Polestar, Savills, Huel).
- **Building ATS job databases** — collect open roles from Teamtailor career sites into one structured dataset.
- **Niche job boards and aggregators** — power a vertical job board (Nordic tech, EU startups, nonprofits) with normalized postings.
- **Recruiting and talent sourcing** — find which companies are hiring for a given role, skill or location.
- **Job market and labour-market research** — analyse hiring trends across Europe and beyond using structured location and date data.
- **Multi-ATS recruitment pipelines** — drop Teamtailor postings into the same pipeline as Greenhouse, Lever, Workable or Recruitee jobs.

### How It Works

![How the Teamtailor Scraper works: public careers feeds become normalized job rows with descriptions, locations and JobPosting data.](https://api.apify.com/v2/key-value-stores/oeuA0kLOyhbRM4fzt/records/how-it-works-jobs-teamtailor-scraper)

Every Teamtailor career site publishes a JSON Feed 1.1 document at `/jobs.json`. The Actor reads each item's inline `content_html` and embedded schema.org JobPosting object, so no second request per job is needed. Company discovery from the public showcase is available as a best-effort option.

Each row covers one job with its UUID, title, company, publish dates, locations, full HTML description, identifier, feed URL and raw JobPosting object.

The actor requests the public JSON Feed 1.1 document that every Teamtailor career site publishes:

```
https://<company>.teamtailor.com/jobs.json
```

It parses each entry in the feed's `items` array. Every item already contains the **full job description** in `content_html` and an embedded schema.org `JobPosting` object under `_jobposting`, with `jobLocation` (an array, so multi-location roles are represented natively) and `hiringOrganization`. Because the description is inline, **no second request per job is needed**.

The crawl is plain HTTP (CheerioCrawler) — no browser, no cookies, no login. The feed is served without bot protection, so no proxy is required.

**Company discovery.** Teamtailor publishes no public directory of customers, so the actor accepts an explicit list of companies in the `companies` input. As a convenience it can also **discover** companies: it reads Teamtailor's public customer showcase page, slugifies each customer name and probes its `/jobs.json` feed. Discovery is best-effort — it only resolves companies whose showcase name maps to their Teamtailor subdomain (in a test run, 12 of 24 showcase customers resolved). For complete coverage, supply your own `companies` list.

**Volume note.** Teamtailor returns up to 100 open jobs per feed page and adds a `next_url` when a company has more. This actor collects the jobs returned by each company's feed page.

### Input Parameters

| Field | Type | Required | Default | Notes |
|-------|------|----------|---------|-------|
| `companies` | string\[] | No | `["career","polestar","savills"]` | Career sites to scrape. Each entry can be a subdomain slug (`"polestar"`), a bare host (`"polestar.teamtailor.com"`) or a full URL (`"https://polestar.teamtailor.com/jobs.json"`). Leave empty to auto-discover companies. |
| `discoverCompanies` | boolean | No | `false` | Also discover companies from Teamtailor's public customer showcase page. Enabled automatically when `companies` is empty. |
| `maxCompanies` | integer | No | `50` | Maximum number of company career sites to scrape in one run. |
| `maxJobs` | integer | No | `1000` | Maximum number of job postings saved to the dataset. Free (non-paying) users are capped at 10 jobs. |
| `proxy` | object (proxy) | No | Apify Proxy off | Standard Apify proxy configuration. Not required — the feed is public and keyless. |

### Output Fields

| Field | Type | Description |
|-------|------|-------------|
| `id` | string | Teamtailor job UUID |
| `title` | string | Job title |
| `url` | string | Public job posting URL |
| `date_published` | string | Feed publish date (ISO 8601) |
| `date_posted` | string | schema.org `datePosted` |
| `valid_through` | string or null | schema.org `validThrough` when present |
| `content_html` | string or null | Full HTML job description |
| `company` | string or null | Hiring organization name |
| `company_slug` | string or null | Teamtailor subdomain slug |
| `company_career_site` | string or null | Company career-site URL (`hiringOrganization.sameAs`) |
| `job_location` | array | Normalized schema.org `PostalAddress` objects |
| `location_strings` | string\[] | Human-readable locations, e.g. `["London, GB"]` |
| `multi_location` | boolean | True when the job has more than one location |
| `location_count` | integer | Number of locations |
| `employment_type` | string or null | schema.org `employmentType` (usually absent in the public feed) |
| `identifier` | object or null | schema.org `PropertyValue` identifier |
| `schema_org` | object or null | The raw schema.org `JobPosting` object |
| `feed_url` | string or null | Source feed URL |
| `scraped_at` | string | Extraction timestamp (ISO 8601) |

### Example Input

```json
{
  "companies": ["career", "polestar", "savills"],
  "discoverCompanies": false,
  "maxCompanies": 50,
  "maxJobs": 1000,
  "proxy": { "useApifyProxy": false }
}
```

To let the actor find companies for you instead:

```json
{
  "discoverCompanies": true,
  "maxCompanies": 50,
  "maxJobs": 200
}
```

### Example Output

```json
{
  "id": "4ff07fd5-3ac0-4333-8f4c-955380396321",
  "title": "UK Account Executive - SMB",
  "url": "https://career.teamtailor.com/jobs/8118064-uk-account-executive-smb",
  "date_published": "2026-07-24T09:05:16+02:00",
  "date_posted": "2026-07-24T09:05:16+02:00",
  "valid_through": null,
  "content_html": "<h4>Let's build the future together!</h4><p>...</p>",
  "company": "Teamtailor",
  "company_slug": "career",
  "company_career_site": "https://career.teamtailor.com",
  "job_location": [
    {
      "streetAddress": "16 Laystall Court",
      "addressLocality": "London",
      "addressRegion": "Europe",
      "postalCode": "EC1R 4",
      "addressCountry": "GB"
    }
  ],
  "location_strings": ["London, Europe, GB"],
  "multi_location": false,
  "location_count": 1,
  "employment_type": null,
  "identifier": { "@type": "PropertyValue", "name": "Teamtailor", "value": 8118064 },
  "schema_org": {
    "@type": "JobPosting",
    "title": "UK Account Executive - SMB",
    "datePosted": "2026-07-24T09:05:16+02:00",
    "hiringOrganization": { "name": "Teamtailor", "sameAs": "https://career.teamtailor.com" }
  },
  "feed_url": "https://career.teamtailor.com/jobs.json",
  "scraped_at": "2026-10-16T09:00:00.000Z"
}
```

### Integrations & Automation

- **Apify API** — start a run programmatically and read results from the default dataset; every run also exposes the dataset as JSON, CSV or Excel.
- **Webhooks** — get notified when a run finishes and push new postings into your own systems.
- **Zapier / Make / n8n** — connect the actor through Apify's no-code integrations to write results to Google Sheets, Airtable, a database or a Slack channel.
- **Scheduling** — for hiring-signal monitoring, run the actor **daily** against your target companies and diff by `id` to surface new openings; run it **weekly** for slower trend tracking.

### Related Actors

- [Career Site Job Listing API](https://apify.com/fantastic-jobs/career-site-job-listing-api) — one schema across dozens of ATS platforms (Teamtailor, Greenhouse, Lever, Workday, Ashby and more); use it when you need many ATS sources in a single run.
- [LinkedIn Jobs Scraper](https://apify.com/curious_coder/linkedin-jobs-scraper) — the broadest jobs source in the Store; pair it with Teamtailor data to cover both aggregators and first-party career sites.
- [BambooHR Scraper](https://apify.com/ahmed_jasarevic/bamboohr-scraper) — BambooHR-hosted job boards, the same structured job schema for a different ATS.
- [Welcome to the Jungle Scraper](https://apify.com/ahmed_jasarevic/welcometothejungle-scraper) — European tech job listings from Welcome to the Jungle.
- [Apna Scraper](https://apify.com/ahmed_jasarevic/apna-scraper) — India blue-collar job listings and salary data.

### Frequently Asked Questions

#### Why use this actor instead of the official Teamtailor API?

The official Teamtailor API is a JSON:API at `api.teamtailor.com` (regional stacks `api.na.teamtailor.com` and `api.au.teamtailor.com`). It requires a **per-tenant API key generated in Settings → Integrations → API keys by a Company Admin**, with Public, Internal or Admin scope — there is no aggregator key that spans multiple companies. This actor instead reads the **keyless public `jobs.json` feed** that each career site publishes, so you can collect jobs from any number of companies without a key and without admin access to their accounts. Use the official API when you own or administer a single Teamtailor account and need write access or non-public data; use this actor for read-only, cross-company public hiring data.

#### What are alternatives to this actor or to the Teamtailor jobs feed?

- **Other Teamtailor scrapers in the Apify Store** — several cover the same public feed; compare on price-per-result, description handling and location parsing.
- **Multi-ATS actors** — e.g. Career Site Job Listing API, which normalizes Teamtailor alongside Greenhouse, Lever, Workable and Recruitee in one schema.
- **The official Teamtailor API** — best when you administer a single account and need non-public fields.
- **Rolling your own** — fetch `https://<company>.teamtailor.com/jobs.json` and follow `next_url` yourself; you then own the parser, HTML stripping and location flattening.

#### How do I scrape Teamtailor job postings?

Pass the company's Teamtailor slug (e.g. `polestar`, `savills`) in the `companies` input and run the actor. Each run returns one row per open job with the description and locations already parsed — no API key, no browser.

#### Does Teamtailor have a public API or a jobs feed?

Teamtailor has an authenticated official API (per-account key required) and, separately, a **public JSON feed** at `/<company>.teamtailor.com/jobs.json` for every career site. This actor uses the public feed.

#### How can I get all jobs from a Teamtailor career site as JSON?

Run the actor with that company's slug; download the dataset as JSON, CSV or Excel from the Apify Console, or read it over the Apify API. Each item includes `content_html` (the full description) plus the raw `schema_org` object.

#### How do I monitor new job openings at a company that uses Teamtailor?

Schedule the actor to run daily against the companies you track, then compare runs by `id` to detect postings that appeared since the previous run.

#### What's the best way to build a job board from Teamtailor career sites?

Run the actor across your target companies (or enable discovery), then map the output fields — `title`, `company`, `location_strings`, `url`, `date_published` and `content_html` — into your board's schema. The dataset's `overview` view already surfaces `title`, `company`, `location_strings`, `date_published` and `url`.

### For AI Agents & LLM Apps

**Purpose:** return one row per open job posting from Teamtailor-hosted career sites (title, URL, publish date, full HTML description, normalized locations, raw schema.org JobPosting).

**Minimal working input:**

```json
{ "companies": ["career"] }
```

**Discovery variant (no company list needed):**

```json
{ "discoverCompanies": true, "maxCompanies": 50, "maxJobs": 200 }
```

**Output fields:** `id`, `title`, `url`, `date_published`, `date_posted`, `valid_through`, `content_html`, `company`, `company_slug`, `company_career_site`, `job_location`, `location_strings`, `multi_location`, `location_count`, `employment_type`, `identifier`, `schema_org`, `feed_url`, `scraped_at`.

**Behaviors an agent should know:**

- If `companies` is empty, company discovery is **enabled automatically** — the actor reads Teamtailor's public showcase page and probes candidate feeds.
- `maxJobs` caps the dataset size. **Free (non-paying) runs are hard-capped at 10 jobs**, regardless of `maxJobs`; only paying runs reach the configured `maxJobs`.
- `maxCompanies` caps how many explicitly provided feeds are scheduled; discovery adds further feed requests on top, bounded by an internal request cap (`maxCompanies + 5`, hard ceiling 500).
- `proxy` defaults to **off**; the feed is public and no proxy is required.
- `employment_type` and `valid_through` are frequently `null` — the public feed usually omits `employmentType` and `validThrough`.
- The actor reads the jobs returned by each company's feed page (Teamtailor returns up to 100 open jobs per page).

**Billing:** pay-per-result — **$1 per 1,000 dataset items** ($0.001 each), plus a small per-run start fee. Budget from the expected number of job rows.

### Legal & Compliance Disclaimer

This actor is an independent tool and is **not affiliated with, endorsed by or sponsored by Teamtailor**.

It accesses only the **publicly available** `jobs.json` feed that Teamtailor career sites publish; it does not log in, bypass authentication, solve CAPTCHAs or access non-public data.

Job data is published for public consumption, but you are responsible for ensuring your use complies with Teamtailor's and each career site's terms of service and with applicable data-protection law (including GDPR where EU personal data is involved).

Job descriptions may contain recruiter or company contact details. Do not use such data for unsolicited commercial outreach in violation of applicable law (e.g. CAN-SPAM, GDPR, TCPA).

### SEO Keywords

teamtailor scraper, teamtailor jobs scraper, teamtailor job scraper api, teamtailor jobs.json feed, scrape teamtailor jobs, teamtailor api alternative, teamtailor career site scraper, teamtailor ats scraping, ats job scraper, job posting scraper, job board data, careers page scraper, jobs feed scraper, hiring data api, recruitment data scraping, job market data, extract job postings, jobs to json, jobs to csv, greenhouse lever workable jobs scraper, nordic jobs data, eu jobs data, polestar jobs, savills careers, hiring signal monitoring

# Actor input Schema

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

Teamtailor company career sites to scrape. Each entry can be a subdomain slug (e.g. "career", "polestar"), a bare host (e.g. "polestar.teamtailor.com") or a full URL (e.g. "https://polestar.teamtailor.com/jobs.json"). Leave empty to auto-discover companies.

## `discoverCompanies` (type: `boolean`):

When enabled, the actor also discovers Teamtailor companies from Teamtailor's public customer showcase page and adds them to the list. Enabled automatically when no companies are provided.

## `maxCompanies` (type: `integer`):

Maximum number of company career sites to scrape in one run.

## `maxJobs` (type: `integer`):

Maximum number of job postings to save to the dataset.

## `proxy` (type: `object`):

Select proxies to be used by your crawler.

## Actor input object example

```json
{
  "companies": [
    "career",
    "polestar",
    "savills"
  ],
  "discoverCompanies": false,
  "maxCompanies": 50,
  "maxJobs": 1000,
  "proxy": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (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": [
        "career",
        "polestar",
        "savills"
    ],
    "proxy": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("ahmed_jasarevic/jobs-teamtailor-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": [
        "career",
        "polestar",
        "savills",
    ],
    "proxy": { "useApifyProxy": False },
}

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

```

## MCP server setup

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