Teamtailor Jobs Scraper & New Job Alerts avatar

Teamtailor Jobs Scraper & New Job Alerts

Pricing

from $1.50 / 1,000 job results

Go to Apify Store
Teamtailor Jobs Scraper & New Job Alerts

Teamtailor Jobs Scraper & New Job Alerts

Scrape all open jobs from any Teamtailor career site (<company>.teamtailor.com or the company's own Teamtailor-powered domain) via the public jobs RSS feed: departments, roles, locations, remote/hybrid status, posting date, descriptions. Filters and new-job monitoring.

Pricing

from $1.50 / 1,000 job results

Rating

0.0

(0)

Developer

Gabor Sziladi

Gabor Sziladi

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Share

Scrape every open job from any Teamtailor career site into a clean dataset: title, department, team, locations, remote flag, employment type, posting date, apply link, full plain-text description, and more. The Actor uses the public Teamtailor jobs RSS feed (/jobs.rss) that every Teamtailor career site publishes, on <company>.teamtailor.com and on custom career domains. It's fast, reliable and cheap: $1.50 per 1,000 jobs.

Turn on Only new jobs and schedule the Actor to get a daily feed of new Teamtailor postings, paying only for the new ones.

  • ✅ Paste Teamtailor URLs or just company slugs
  • ✅ All open jobs, one normalised record per job
  • ✅ Filters: keywords, exclude keywords, locations, remote only, posted within N days
  • ✅ Only new jobs monitoring mode for alerts, webhooks, Slack, Google Sheets, Zapier or Make
  • ✅ One broken company never fails the run; errors are listed in the OUTPUT summary
  • ✅ No login, no proxies, no browser. Polite, rate-limited requests to the official endpoint.

Need other ATS platforms too? The all-in-one ATS Jobs Scraper (sysco32/ats-jobs-feed) covers 9 platforms (Greenhouse, Lever, Ashby, Workday, SmartRecruiters, Workable, Recruitee, Personio and Teamtailor) and auto-detects the ATS from any careers URL.

What data you get

Teamtailor is the employer-branding ATS used by many Nordic and European companies. The feed publishes all locations (city and country), department, role (returned as team), remote status (remote / hybrid / onsite), the publication date and the full description. One request per company returns every job. Teamtailor does not publish salary or employment type in its feed.

FieldExample
company, company_slugCompany name and Teamtailor identifier
job_id, requisition_idStable IDs for deduplication
title, department, teamJob title and organisation
location, locations[], remote, workplace_typeAll locations plus remote / hybrid / onsite
employment_typeFull-time, part-time, contract… when published
posted_at, updated_atISO 8601 UTC
salary{min, max, currency, period, text} when published
job_url, apply_urlDirect links
description_text (+ optional description_html)Full job description

Input example

{
"companies": [
"https://polestar.teamtailor.com",
"oatly",
"lunar",
"instabee"
],
"keywords": [
"engineer"
],
"remoteOnly": false,
"maxJobsPerCompany": 100,
"includeDescription": true,
"onlyNewJobs": true
}

You can paste: https://polestar.teamtailor.com, a job URL, a custom career domain that runs on Teamtailor (https://careers.<company>.com), or just the subdomain (oatly).

Output example (real run)

{
"company": "Oatly AB",
"company_slug": "oatly",
"ats": "teamtailor",
"job_id": "8575321",
"requisition_id": null,
"title": "Brand Manager (m/w/d) - AT & CH",
"department": "Brand & Creative",
"team": "Brand Activation",
"location": "Wien, Austria",
"locations": [
"Wien, Austria"
],
"remote": false,
"workplace_type": "hybrid",
"employment_type": null,
"posted_at": "2026-10-20T10:37:15Z",
"updated_at": null,
"salary": null,
"job_url": "https://careers.oatly.com/jobs/8575321-brand-manager-m-w-d-at-ch",
"apply_url": "https://careers.oatly.com/jobs/8575321-brand-manager-m-w-d-at-ch/applications/new",
"description_text": "“A Company built on the idea of change.”\nJa, wir wissen schon, das sind große Worte. Aber vielleicht ist es ja gar nicht mal zu weit aus dem Fenster gelehnt, wenn wir uns als Pi-oat-niere der Post Milk Generation bezeich…",
"description_html": null,
"source_input": "oatly",
"scraped_at": "2026-10-21T18:15:21Z"
}

Download the results as JSON, CSV, Excel or XML, or read them through the Apify API. A per-company summary (jobs found, jobs written, errors) is saved to the OUTPUT record of the run's key-value store.

Pricing

Pay per event, no subscription:

EventPrice
Job result (one job in the dataset)$0.0015 ($1.50 per 1,000 jobs)
Actor start (per run)$0.002

For example, 500 jobs cost about $0.75. A daily Only new jobs monitor that finds 20 new jobs costs about $0.03 per run. Failed companies are never charged, and you can set a maximum cost per run.

Use cases

  • Track hiring at Nordic and European companies on Teamtailor, such as Polestar, Oatly, Lunar, Instabee, Qliro and Anyfin.
  • Build niche job boards and newsletters from a list of target employers.
  • Sales and recruiting intelligence: hiring is a buying signal, so see which accounts are hiring, for which teams and where.
  • Job alerts for yourself or your candidates via Only new jobs plus a schedule.
  • Feed clean job data to AI agents, RAG pipelines and spreadsheets.

FAQ

Is this legal? The Actor reads only the public job-board endpoint that Teamtailor provides so job postings can be displayed on career sites and job boards. No login and no personal data, apart from what employers publish in their job ads. You are responsible for how you use the data.

What if the company uses its own careers domain? Paste it (for example https://jobs.lunar.app). The Actor detects that the site runs on Teamtailor and reads its feed. Otherwise use https://<company>.teamtailor.com or just <company>.

Why does a company return no jobs? Some companies use Teamtailor only for employer branding and disable the public feed. The run still succeeds and the company is listed in OUTPUT.errors with the reason.

How does "Only new jobs" work? The Actor remembers the job IDs it has already delivered for each company in a named key-value store (stateStoreName). Later runs output only unseen jobs. The first run returns everything that matches, and closed jobs drop out of the state automatically. Jobs held back by Max jobs per company are delivered in the next run.

One company failed. What happens? It's logged and listed in OUTPUT.errors, and the other companies are still processed. If you paste a URL from another ATS, the error message points you to sysco32/ats-jobs-feed.