Teamtailor Jobs Scraper: Job Listings from Company Career Sites

Get every published job from the Teamtailor career sites of the companies you choose, as clean, flat JSON, CSV or Excel. This Teamtailor jobs scraper reads the job feed Teamtailor publishes for every career site (<company>.teamtailor.com/jobs.rss), the feed Teamtailor documents for sharing a company's open jobs, so it is fast and does not break when a careers page changes its design. One request returns up to 100 jobs with their full texts; list as many companies as you like in one run.

Each job comes with title, department, role, every office with its city and country code, the remote status (remote, hybrid, on-site), the publication date and the full ad text.

What you get

Price: $1.50 per 1,000 job ads on the Free plan, $1.00 on the Business plan, paid per row delivered; the $5 monthly credit of a free Apify account covers about 3,300 job ads. Details in Pricing below.

One row per job:

• Job: id (teamtailor:company:jobId), title, job page (on the company's own domain when it has one), company name as shown on its career site
• Classification: department, role (team), workplace type (remote, hybrid, on-site) and remote flag; the division and Teamtailor's own remote value in metadata
• Location: every office of the job, plus country, ISO country code, region and city of the first one
• Dates: published
• Text: the ad as plain text, optional HTML

Teamtailor's feed carries no salary and no employment type, so those columns stay empty; when an employer writes them in the ad, they are in the text.

Why this actor

• One request per 100 jobs: the feed carries the full ad text, so there are no detail requests to wait for.
• Structured locations: city and country come from the offices Teamtailor stores for each job, not guessed from free text, so country filters are exact.
• Career sites on their own domain work too: paste https://jobs.tibber.com and the actor checks that the domain serves a Teamtailor feed, then reads it there; the rows keep the links on the company's domain.
• Contact details removed from texts, a report per company and a charge cap: you pay per delivered job ad.

How to use it

1. Open the Actor and fill in Companies (the other fields are optional filters).
2. Set Maximum job ads to a small number for a first try (the default is a safe start).
3. Click Start. The status line shows progress; the run stops cleanly at your limit or at the charge limit you set in the run options.
4. Open the Dataset tab and download JSON, CSV, Excel, XML or HTML, or send the rows to Google Sheets, Slack, Make, n8n or Zapier with the Integrations tab.
5. To run it on a schedule, use Schedules in Apify Console and turn on Only new rows since the last run below: every run then costs only the new rows, and a webhook URL tells you when something new came in.

Input

Quick start. This input is ready to run (it is also the example in the API tab):

{
  "companies": [
    "deezer",
    "polestar",
    "tibber"
  ],
  "maxItems": 100
}

One real row it returns (long texts shortened here):

{
  "id": "teamtailor:tibber:8497810",
  "jobId": "8497810",
  "ats": "teamtailor",
  "company": "tibber",
  "companyName": "Tibber",
  "title": "Senior Engineering Manager",
  "url": "https://jobs.tibber.com/jobs/8497810-senior-engineering-manager",
  "applyUrl": "https://jobs.tibber.com/jobs/8497810-senior-engineering-manager",
  "requisitionCode": null,
  "department": "House of Product & Engineering",
  "departments": [
    "House of Product & Engineering"
  ],
  "team": "Engineering Manager",
  "employmentType": null,
  "workplaceType": "Hybrid",
  "isRemote": false,
  "location": "Berlin, Germany · Stockholm, Sweden",
  "locations": [
    {
      "raw": "Berlin, Germany",
      "country": "Germany",
      "countryCode": "DE",
      "region": null,
      "city": "Berlin"
    },
    {
      "raw": "Stockholm, Sweden",
      "country": "Sweden",
      "countryCode": "SE",
      "region": null,
      "city": "Stockholm"
    }
  ],
  "country": "Germany",
  "countryCode": "DE",
  "region": null,
  "city": "Berlin",
  "publishedAt": "2026-10-05T09:32:43.000Z",
  "updatedAt": null,
  "language": null,
  "salaryMin": null,
  "salaryMax": null,
  "salaryCurrency": null,
  "salaryPeriod": null,
  "salaryText": null,
  "descriptionText": "We're at a pivotal moment for both Tibber and the planet. When joining Tibber, you won’t just help scale a forward-thinking tech company…",
  "requirementsText": null,
  "benefitsText": null,
  "metadata": {
    "remoteStatus": "hybrid"
  },
  "detailsIncluded": false
}

Field	What it does
companies	Company names (deezer), career-site addresses (polestar.teamtailor.com, or the company's own domain such as https://jobs.tibber.com) or job links (then only that job)
keywords	Match the job title; keywordsInDescription also searches the ad text
locations	Countries, codes, regions or cities; add remote to keep remote jobs
departments, remoteOnly, postedAfter	More filters (departments also matches the role; postedAfter: 2026-10-01, yesterday, 7 days)
maxItems, maxItemsPerCompany, includeHtml	Limits (0 = none); HTML text
onlyNew, stateName, notifyUrl, notifyWhenEmpty	See Automation below

Example: jobs in Germany or Sweden from three companies, posted in the last 30 days.

{
  "companies": ["polestar", "tibber", "deezer"],
  "locations": ["Germany", "Sweden"],
  "postedAfter": "30 days"
}

Output

37 fields per row. Empty values are null, never missing, so CSV and Excel columns are stable.

Field	Type	Example
id	string	greenhouse:stripe:8172510
jobId	string	8172510
ats	string	greenhouse
company	string	stripe
companyName	string	Stripe
title	string	Abuse Investigator
url	string	Job page
applyUrl	string	Apply page
requisitionCode	string	Requisition code
department	string	Department (first)
departments	array	All departments
team	string	Team or function
employmentType	string	Full-time
workplaceType	string	Workplace type: Remote, Hybrid, On-site, or as written
isRemote	boolean	False
location	string	Dublin · Ireland
locations	array	Locations: raw text, country, countryCode (ISO 3166-1), region, city
country	string	Ireland
countryCode	string	IE
region	string	Region or state of the first location
city	string	Dublin
publishedAt	string	2026-09-03T17:30:34.000Z
updatedAt	string	Last update (when the system publishes it)
language	string	en
salaryMin	number	Salary from (when the employer publishes it)
salaryMax	number	Salary to
salaryCurrency	string	Salary currency (ISO 4217)
salaryPeriod	string	Salary period: year, month, week, day, hour
salaryText	string	Salary as the employer wrote it
descriptionText	string	Full ad text as plain text, contact details removed
requirementsText	string	Requirements as a separate text (Lever, Workable, Recruitee, Personio, when the employer separates them)
benefitsText	string	Benefits as a separate text (Lever, Workable, Personio, when separated)
descriptionHtml	string	HTML version of the description (only with "Include HTML")
requirementsHtml	string	HTML version of the requirements (only with "Include HTML")
benefitsHtml	string	HTML version of the benefits (only with "Include HTML")
metadata	object	Other fields the employer set: custom fields, level, category, experience, hours per week, keywords
detailsIncluded	boolean	False

Example rows

Two real rows from a run (long texts shortened here, complete in the dataset):

[
  {
    "id": "teamtailor:tibber:8497810",
    "jobId": "8497810",
    "ats": "teamtailor",
    "company": "tibber",
    "companyName": "Tibber",
    "title": "Senior Engineering Manager",
    "url": "https://jobs.tibber.com/jobs/8497810-senior-engineering-manager",
    "applyUrl": "https://jobs.tibber.com/jobs/8497810-senior-engineering-manager",
    "requisitionCode": null,
    "department": "House of Product & Engineering",
    "departments": [
      "House of Product & Engineering"
    ],
    "team": "Engineering Manager",
    "employmentType": null,
    "workplaceType": "Hybrid",
    "isRemote": false,
    "location": "Berlin, Germany · Stockholm, Sweden",
    "locations": [
      {
        "raw": "Berlin, Germany",
        "country": "Germany",
        "countryCode": "DE",
        "region": null,
        "city": "Berlin"
      },
      {
        "raw": "Stockholm, Sweden",
        "country": "Sweden",
        "countryCode": "SE",
        "region": null,
        "city": "Stockholm"
      }
    ],
    "country": "Germany",
    "countryCode": "DE",
    "region": null,
    "city": "Berlin",
    "publishedAt": "2026-10-05T09:32:43.000Z",
    "updatedAt": null,
    "language": null,
    "salaryMin": null,
    "salaryMax": null,
    "salaryCurrency": null,
    "salaryPeriod": null,
    "salaryText": null,
    "descriptionText": "We're at a pivotal moment for both Tibber and the planet. When joining Tibber, you won’t just help scale a forward-thinking tech company…",
    "requirementsText": null,
    "benefitsText": null,
    "metadata": {
      "remoteStatus": "hybrid"
    },
    "detailsIncluded": false
  },
  {
    "id": "teamtailor:tibber:8318649",
    "jobId": "8318649",
    "ats": "teamtailor",
    "company": "tibber",
    "companyName": "Tibber",
    "title": "Backend Engineer",
    "url": "https://jobs.tibber.com/jobs/8318649-backend-engineer",
    "applyUrl": "https://jobs.tibber.com/jobs/8318649-backend-engineer",
    "requisitionCode": null,
    "department": "House of Product & Engineering",
    "departments": [
      "House of Product & Engineering"
    ],
    "team": "Backend Engineer",
    "employmentType": null,
    "workplaceType": "Hybrid",
    "isRemote": false,
    "location": "Berlin, Germany · Stockholm, Sweden",
    "locations": [
      {
        "raw": "Berlin, Germany",
        "country": "Germany",
        "countryCode": "DE",
        "region": null,
        "city": "Berlin"
      },
      {
        "raw": "Stockholm, Sweden",
        "country": "Sweden",
        "countryCode": "SE",
        "region": null,
        "city": "Stockholm"
      }
    ],
    "country": "Germany",
    "countryCode": "DE",
    "region": null,
    "city": "Berlin",
    "publishedAt": "2026-09-03T15:51:22.000Z",
    "updatedAt": null,
    "language": null,
    "salaryMin": null,
    "salaryMax": null,
    "salaryCurrency": null,
    "salaryPeriod": null,
    "salaryText": null,
    "descriptionText": "We're at a pivotal moment for both Tibber and the planet. When joining Tibber, you won’t just help scale a forward-thinking tech company…",
    "requirementsText": null,
    "benefitsText": null,
    "metadata": {
      "remoteStatus": "hybrid"
    },
    "detailsIncluded": false
  }
]

Results can be downloaded as JSON, CSV, Excel, XML or HTML from the Dataset tab, or read through the Apify API.

Pricing

Pay per result. You pay for each job ad delivered to your dataset, nothing else: no subscription, no minimum, no charge for rows your filters drop or for the requests behind them.

Your Apify plan	Price per 1,000 rows	Price per row
Free plan	$1.50	$0.0015
Starter plan	$1.33	$0.00133
Scale plan	$1.17	$0.00117
Business plan and above	$1.00	$0.001

Example: 1,000 job ads cost $1.50 on the Free plan and $1.00 on the Business plan. Platform usage of the run (compute, storage) is included in that price and is not billed to you separately (pay per event: the actor covers it). A start event of $0.00005 is charged once per run (Apify default). Cap your spend: set Maximum total charge in the run options. The actor stops cleanly when the cap is reached and you keep everything delivered until then. The run summary (RUN_SUMMARY in the key-value store) says why a run stopped.

Automation: only new rows, notifications, schedules

Only new rows since the last run. Turn on onlyNew and the actor remembers every job ad it delivered to you (in a key-value store named rowcraft-teamtailor-jobs-scraper-state in your Apify account). The next run with the same stateName skips what you already have and you pay only for new rows. The first run delivers everything that matches. Use a different stateName for each schedule or search so they keep separate memories.

Notification when the run ends. Put a webhook address in notifyUrl and the actor sends one JSON POST with the number of new rows, links to the dataset (JSON and CSV) and the run. It works out of the box with Slack and Discord incoming webhooks (the message is in text and content), with Make, n8n and Zapier catch hooks, and with your own endpoint. By default it is sent only when there is at least one new row; notifyWhenEmpty sends it every time.

Schedules. Create a schedule in Apify Console (hourly, daily, weekly or cron) with onlyNew on. A daily schedule gives you a feed of new job ads for the price of the new rows only.

Integrations. Send the results to Make, n8n, Zapier, Google Sheets, Slack, Google Drive, Airtable or any webhooks from the Integrations tab of the Actor, with no code. Apify also offers native actions for Make, n8n and Zapier.

API, SDKs and AI agents. Every run is available through the Apify API and the official JavaScript and Python clients; the Actor can also be called by AI agents through the Apify MCP server. The example input in the API tab is a working call.

Use with AI agents (MCP). Add the Apify MCP server to Claude, Cursor, VS Code or any MCP client and the agent can run this Actor as a tool:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=rowcraft/teamtailor-jobs-scraper",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

Call it from a shell or any language. One request runs the Actor with the input below and returns the rows as JSON:

curl -X POST "https://api.apify.com/v2/acts/rowcraft~teamtailor-jobs-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"companies": ["deezer", "polestar", "tibber"], "maxItems": 100}'

Python (pip install apify-client):

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("rowcraft/teamtailor-jobs-scraper").call(run_input={'companies': ['deezer', 'polestar', 'tibber'], 'maxItems': 100})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript / Node.js (npm install apify-client):

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('rowcraft/teamtailor-jobs-scraper').call({"companies": ["deezer", "polestar", "tibber"], "maxItems": 100});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Use cases

• Job boards and aggregators: a clean feed from the Teamtailor companies you follow, many of them European and Nordic employers.
• Hiring signals: which teams and offices a company is hiring for, and how that changes week by week.
• Monitoring: only new rows tell you when a company opens a matching role.

Ready-made examples, each with the input filled in (open one and press Start, or save it as your own task):

• Get jobs at Nordic companies hiring on Teamtailor
• Get jobs in Stockholm from Teamtailor career sites

What this actor does not do

• Search all of Teamtailor by keyword: you bring company names, and the filters apply to them.
• Read applications, candidates, recruiters, the application form or internal jobs (robots.txt excludes /jobs/internal/, and the actor never asks for it).
• Deliver salaries or employment types: Teamtailor's feed has neither.
• Read career sites on other systems: a domain without a Teamtailor feed answers not_found, and addresses of other job systems (Greenhouse, Lever…) are listed as invalid.
• Report closed jobs: a job that disappears is simply missing from the next run.

Limits and fair use

• One request per second by default, 250 ms at the lowest. A request returns up to 100 jobs: Deezer had 16 published jobs and Schibsted 37 on 12 October 2026, one request each.
• Keyword, location, department and date filters run on the feed; only delivered jobs are charged.
• If the site shows an anti-bot page or asks for a long pause, the actor stops and keeps what it delivered (stoppedByProtection, stoppedByRateLimit in the run summary).

Data source

Source: the Teamtailor job feed of each career site (<company>.teamtailor.com/jobs.rss, 100 jobs per page with offset and per_page), which Teamtailor documents in its help centre for sharing a company's published jobs (RSS feed guide); the guide notes that all of the data in the feed is publicly available. The career sites' robots.txt allows the feed. No login or cookie. The job ads belong to the employers; each row links to the original. Rowcraft is not affiliated with Teamtailor; the name belongs to its owner.

Privacy: no personal data

Rowcraft actors are built not to collect personal data:

• The feed has no recruiter or applicant fields, and the office street address and postcode are not delivered (city and country are).
• E-mail addresses, phone numbers, mailto:, tel: and personal LinkedIn links in ad texts are removed; contact-person names after a title or contact cue ("Recruiter: …") become [name removed]. Other names cannot be told from ordinary words reliably.

You are responsible for using the data in line with the law that applies to you.

Other Rowcraft actors

Related Rowcraft actors. All of them read official or public sources, deliver flat rows without private contact details and support only-new runs and notifications; the full list is on the Rowcraft profile:

• Ashby Jobs Scraper – Job Postings with Salary Ranges — Job postings from Ashby job boards (jobs.ashbyhq.com) by company: title, department, team, locations with country, employment and workplace type, published salary range, full text.
• Career Site Jobs Scraper: Greenhouse, Lever, Ashby, Workday — Jobs from the career pages of the companies you choose: give a name or website and the actor finds the system (Greenhouse, Lever, Ashby, Workday, Workable, Personio, Recruitee, Teamtailor, Gem).
• Gem Jobs Scraper – Job Board Listings from jobs.gem.com — Job listings from Gem job boards (jobs.gem.com) by company: title, department, offices with country, employment type, remote, hybrid or on-site, requisition ID, publication date and full ad text, from the public Gem Job Board API.
• Greenhouse Jobs Scraper by Company — Job listings from Greenhouse job boards by company: title, departments, offices, publication date, full ad text, published pay ranges.
• Himalayas Jobs Scraper: Remote Jobs API with Salaries — Remote jobs from Himalayas through its public jobs API: title, company, salary range, seniority, categories, the countries and time zones open to candidates, full description and job link.
• Lever Jobs Scraper for Any Company — Job postings from Lever career pages (jobs.lever.co) by company: title, team, department, location, commitment, workplace type, salary range when published, description, requirements and benefits.

FAQ

What do I put in Companies? The careers page address as you see it: deezer.teamtailor.com (or just deezer), or the company's own domain when its Teamtailor career site lives there (https://jobs.tibber.com; the Teamtailor link at the bottom of the page, "Applicant tracking system", tells you it is one). A job link (…/jobs/<number>-<title>) reads only that job. The same company given both ways is read twice, with different row ids.

Why are salary and employment type empty? Teamtailor's feed does not carry them. Employers who publish a salary or a contract type write it in the ad, which you get in descriptionText; keywordsInDescription can search it.

What are remote, hybrid and on-site? Teamtailor stores a remote status for each job: fully remote becomes Remote, hybrid Hybrid, on-site On-site, and any other value is kept as written; a job where the employer left it unset (none) has workplaceType empty. The original value is in metadata.remoteStatus; remoteOnly keeps the remote jobs.

How do I get only new jobs on a schedule? Turn on onlyNew, give each schedule its own stateName and add a schedule in Apify Console. The actor remembers every job id, so an edited ad is not delivered or charged again.

How fast is it, and are there limits? One request per company up to 100 jobs and one request per second, no proxies; a hundred companies take under two minutes.

What happens when a company name is wrong? The COVERAGE record and the run summary give each company a status: ok, empty (no published jobs, or the job of a job link has closed: its id is listed in missingJobLinks), not_found, failed (with the reason) or not_reached (the run stopped before it). A name Teamtailor does not know answers not_found.

In which language are the texts? In the language the employer published the job in; Teamtailor's feed gives each job once.

How much does it cost? $1.50 per 1,000 job ads on the Free plan, less on paid plans (see Pricing). You pay only for rows delivered to your dataset; set a maximum total charge in the run options to cap a run.

How do I get the results into Slack, Google Sheets, Make, n8n or Zapier? Use the Integrations tab of the Actor for the data, and the notifyUrl field for a message when a run ends (Slack and Discord webhooks work directly; catch hooks of Make, n8n and Zapier too).

Can I call it from code or from an AI agent? Yes: through the Apify API, the JavaScript and Python clients, and the Apify MCP server. The API tab shows a working example with the input of this Actor.

Is it legal to use this data? The actor reads the official API described in the Data source section and delivers company and job data without personal data. The licence of the source is described above. How you use the data is your responsibility under the law that applies to you.

Does it collect personal data? No. Contact persons, e-mails and phone numbers are removed and fields about people are never requested. See the Privacy section.

The run finished with 0 rows. Did I pay? No: with no rows delivered nothing is charged apart from the start event. Check the run summary (RUN_SUMMARY) for warnings, widen the filters, or run with Only new rows off if everything matching was already delivered to you.

Support and reviews

Problems, missing fields, questions: open an issue on the Issues tab of this Actor. We answer within one working day and fix confirmed bugs in the next release; the changelog lists every change.

If this Actor saved you time, a short review on its page helps other users find it and helps us keep improving it.