Teamtailor Job Scraper — Nordic & European Careers Sites 🚀

foXLabs hiring series: Greenhouse · Lever · Ashby · Workday · SmartRecruiters · Personio

🎉 Turn any company's Teamtailor board into clean, structured hiring data — no login, no API key, one row per open role. Built for recruiters, sales & competitive-intelligence teams, and anyone scoring hiring intent at scale.

🔍 What is the Teamtailor Job Board Scraper — and when should you use it?

Teamtailor is the ATS of choice across the Nordics and much of European scale-up hiring. Point this actor at a careers domain (career.kry.se) and it returns every open role — title, location (city & country), posted date, full description and apply link — including the custom domains companies use instead of a teamtailor.com subdomain.

Use it when you need: every open role at a target company, hiring-intent signals (which functions a company is growing), a recruiter sourcing list across many companies, or a clean read of a competitor's headcount plans — from the JSON Feed every Teamtailor careers site publishes at /jobs.json, no key.

Use something else when: the company doesn't run on Teamtailor. Point the matching actor at its ATS instead — every actor in the foXLabs hiring series emits the same schema, so their outputs concatenate into one hiring-intent table: Greenhouse · Lever · Ashby · Workday · SmartRecruiters · Personio.

🤖 Use with AI agents

Already on the Apify MCP server? Ask for this Actor by name: foxlabs/teamtailor-job-board-scraper.

Your agent can pay for its own runs. This Actor is pay-per-event with agentic payments, so an agent can discover it, run it and settle the bill over x402 (USDC on Base) or Skyfire — no Apify account or API token of its own. Billing is per delivered role, never for errors.

Otherwise paste this into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

I want to pull a company's open roles using the Apify Actor `foxlabs/teamtailor-job-board-scraper`.
Input: `queries` is a list of a Teamtailor careers hostname or URL (`career.kry.se`). `maxResultsPerQuery` caps rows per company (default 200).
Start with: {"queries":["career.kry.se"],"maxResultsPerQuery":50}
Ask me which companies to track, run the Actor, then summarise the roles as a table.

The machine-readable API, MCP config and OpenAPI definition live at apify.com/foxlabs/teamtailor-job-board-scraper.md.

📋 Overview

Everything you need to turn a Teamtailor careers board into clean, structured data — role details, metadata and hiring signals — in one actor, with no login, cookies or API key.

Why teams pick this actor:

• ✅ Whole board in one call — every open role, no per-tool stitching.
• ⚡ Slug- or URL-native — paste what you already have; the actor resolves the rest.
• 📄 Complete descriptions — full role text, HTML stripped to clean plain text.
• 🔗 Same schema across the series — join with the six sibling ATS actors on companyBoard.
• 💰 Pay only for results — per-row pricing, empty/failed lookups never billed.
• 🤖 Agent-ready — MCP + x402 agentic payments.
• 🇸🇪 Nordic coverage — the best public read on Swedish, Norwegian, Danish and Finnish scale-up hiring.
• 📍 Real locations — city and country parsed from the feed's structured schema.org data.

🎬 Quick Start

curl -X POST "https://api.apify.com/v2/acts/foxlabs~teamtailor-job-board-scraper/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries":["career.kry.se"],"maxResultsPerQuery":50}'

🚀 Getting Started (3 steps)

1. Choose your companies — a Teamtailor careers hostname or URL (career.kry.se).
2. Set the cap — maxResultsPerQuery limits rows per company (default 200).
3. Run and export — a clean dataset as JSON, CSV or Excel.

📥 Input

{
  "queries": [
    "career.kry.se",
    "https://jobs.lunar.app",
    "https://jobs.tibber.com"
  ],
  "maxResultsPerQuery": 200,
  "maxConcurrency": 5,
  "includeRaw": false
}

Field	Type	Description
queries	array	a Teamtailor careers hostname or URL (career.kry.se).
maxResultsPerQuery	integer	Caps rows per company (default 200).
maxConcurrency	integer	How many companies to fetch at once.
includeRaw	boolean	Attach the source's untouched record under raw.
requestDelayMs	integer	Politeness delay between requests.
proxyConfiguration	object	Optional.

📤 Output

One row per open role, saved to the dataset.

Field	Type	Description
companyName	Company name
companyBoard	Careers hostname — join key
jobId	Teamtailor posting ID
jobTitle	Role title
location	Primary location (city, region, country)
city	City
postalCode	Postal code
countryName	Country code
allLocations	All posting locations
isRemote	Remote flag
postedAt	Published date (ISO)
description	Full description, HTML stripped
applyUrl	Apply link
sourceUrl	Public posting URL

Every row also carries query, scrapedAt, and — when a lookup fails — an error.

💼 Use cases

1. Nordic market hiring intent Input: target careers domains, weekly. Output: roles by function + location. Use: the best public read on Nordic scale-up hiring.

2. Competitor tracking Input: a peer's careers domain. Output: role list over time. Use: watch which functions grow week over week.

3. Recruiter sourcing Input: several careers domains. Output: roles + apply links. Use: source across Nordic employers.

🔗 Integration

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/teamtailor-job-board-scraper').call({ queries: ['career.kry.se'], maxResultsPerQuery: 50 });
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('foxlabs/teamtailor-job-board-scraper').call(run_input={'queries': ['career.kry.se'], 'maxResultsPerQuery': 50})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

Automation (n8n / Zapier / Make): schedule or webhook → HTTP request to the actor API → handle the JSON dataset → push to a sheet, CRM or dashboard.

📊 Pricing

Pay-per-event: $0.002 per delivered role. Empty or failed lookups are never billed. View current pricing.

❓ FAQ

Do I need an account, login or API key? No. This reads the JSON Feed every Teamtailor careers site publishes at /jobs.json — no key.

What do I search by? A Teamtailor careers hostname or URL (career.kry.se).

How current is the data? Every run queries the source live, so results are as fresh as the board itself.

Can I export to CSV / Excel / JSON? Yes — directly from the Apify dataset.

What happens on a bad input or empty board? You get a row with your query and an error — nothing is silently dropped, and you're not charged.

Is scraping this legal? It reads a public job feed the company publishes for syndication — job data, not personal data. See below.

🐛 Troubleshooting

• "… is not a Teamtailor job feed" — pass the careers hostname (the actor appends /jobs.json); custom domains and company.teamtailor.com both work.
• Fewer rows than expected — raise maxResultsPerQuery.
• An error row — the hostname is not a Teamtailor site.

⚠️ Trademark

Independent, third-party tool. Not affiliated with, endorsed by or connected to Teamtailor AB. "Teamtailor" and related marks belong to their owners and are used here for identification only.

⚖️ Is it legal to scrape this data?

This actor reads only publicly published job-posting data — no private or personal user data. Your results can still contain personal data (e.g. a name in a description); personal data is protected by the GDPR and similar laws, so only process it with a legitimate basis. See Apify's blog post on the legality of web scraping.

🤝 Support & contact

• 🌐 Website: data.foxlabs.com.tr
• 📧 Email: info@foxlabs.com.tr
• 🐛 Issues: open a ticket in the Actor's Issues tab
• 🧰 More clean B2B data actors: Fox Labs on Apify

Changelog

0.4.1 — 2026-09-06

• Added postalCode. Postal code from the structured job location (100% of roles), for precise geo alongside city / country.

0.4 — 2026-09-06

• Enabled AI-agent payments (x402). Standby mode was removed because Apify's x402 agentic-payment eligibility requires it off; the actor now runs as a standard pay-per-event run that agents can discover, run and pay for over x402 (USDC on Base) or Skyfire without an Apify account. Batch and MCP usage are unchanged.

0.3 — 2026-09-05

• Output schema linked in actor.json (output field) so the Store shows the Output tab.
• Standby mode (real-time API). The actor now also runs as an always-on HTTP API: GET /search?query=<query>&maxResults=N returns open roles as JSON, billed per role (pay-per-event). Batch runs are unchanged. Endpoint and OpenAPI schema appear in the Standby tab.

0.2 — 2026-09-05

• Real locations added. Location, city and country now come from the feed's schema.org JobPosting data (jobLocation); the old code read the JSON Feed tags array, which current Teamtailor sites leave empty, so location was always blank. Adds allLocations for multi-site roles.
• Dead columns removed. department, team, employmentType, seniority, salary, updatedAt, tags, author (none present in the current feed) are no longer emitted.

0.1

• Initial release: roles from any Teamtailor careers site JSON feed (title, description, dates).