Teamtailor Job Scraper | $1.50/1K — Nordic ATS, No Login

If you track which Scandinavian tech companies are hiring — or build tools for Nordic talent sourcing — this is your fastest data source.

Pricing: $1.50/1,000 jobs (Pay-Per-Event — you pay only for results delivered)

Scrape job postings from any Teamtailor-powered company career page via the public jobs.json feed — No API key. No login. No proxy. No account. Batch multiple companies in a single run and get a clean, enriched dataset ready for pipelines, dashboards, or lead generation.

What is Teamtailor?

Teamtailor is a Scandinavian ATS (Applicant Tracking System) used by thousands of companies — especially Nordic startups and scale-ups — to power their career sites. Every Teamtailor company exposes a public JSON Feed at /<slug>.teamtailor.com/jobs.json or at a custom career domain.

What data does this scraper return?

Each job posting returns 19 fields:

Field	Example
title	"Senior Software Engineer"
company	"Hemnet"
location	"Stockholm, SE"
city	"Stockholm"
country	"SE"
remote_type	"remote" / "hybrid" / null
seniority	"senior" / "manager" / "intern" / "mid"
department	null (not in public feed)
employment_type	null (not in public feed)
posted_at	"2026-05-28T13:06:16+02:00"
url	"https://hemnet.teamtailor.com/jobs/1234-product-manager"
apply_url	same as url
job_id	"1234"
global_id	"teamtailor:hemnet:1234"
description_text	Full plain-text description (HTML stripped)
description_html	Full raw HTML description
parse_confidence	0.0–1.0 quality score
warnings	List of quality flags
scraped_at	ISO timestamp of the run

Why parse_confidence?

Every row carries a quality score from 1.0 (all key fields present) down to 0.0. If a job is missing a title, URL, or description, the score drops and a warning code is added. Filter on parse_confidence >= 0.9 for highest-quality rows. No competitor includes this signal.

How to specify companies

Pass Teamtailor slugs in the companies input:

hemnet        → hemnet.teamtailor.com/jobs.json
storytel      → storytel.teamtailor.com/jobs.json
hedvig        → hedvig.teamtailor.com/jobs.json

Custom career domains also work:

career.teamtailor.com   → career.teamtailor.com/jobs.json

Input parameters

Parameter	Type	Default	Description
companies	string list	—	Teamtailor slugs or custom career domains
titleKeyword	string	—	Filter by job title (case-insensitive)
locationKeyword	string	—	Filter by location, city, or country
remoteOnly	boolean	false	Only return remote jobs
maxJobsPerCompany	integer	50	Cap per company (0 = unlimited)
includeDescriptions	boolean	true	Include full HTML + text descriptions

Use cases

• Talent sourcing — monitor specific companies for new roles in your target domain
• Lead generation — find hiring companies in a vertical (fintech, SaaS, gaming)
• Competitive intelligence — track hiring trends across Teamtailor-powered companies
• Job board aggregation — feed a niche job board with Nordic/European tech jobs
• Change detection — run daily and compare job_id sets to detect new openings

Zero infrastructure cost

The Teamtailor jobs.json feed is:

• 100% public — no API key, no login, no account required
• Zero proxy cost — regular HTTP fetch, no access restrictions
• Full descriptions inline — no second detail-page call needed
• Schema.org structured data — city, country, company name parsed from machine-readable markup

Seniority classification

Every job title is classified into one of 11 levels: executive, vp, director, manager, principal, staff, lead, senior, intern, entry, mid. Useful for filtering senior-only or entry-level roles without parsing titles yourself.

Pricing example

Run	Jobs returned	Cost
Trial (1 company, default 50 cap)	50	~$0.08
1,000 jobs (20 companies)	1,000	$1.50
10,000 jobs (200 companies)	10,000	$15.00

Pay per result via Apify's Pay-Per-Event model. You only pay for jobs actually returned to your dataset — no charge for empty companies or filtered-out rows.

FAQ

Do I need an API key or proxy? No. The Teamtailor jobs.json feed is fully public — no credentials, no proxy, no browser needed.

What formats can I export? JSON, CSV, Excel, or JSONL — all available directly from the Apify dataset UI or via API.

Can I schedule daily monitoring runs? Yes. Use Apify Schedules to run daily and compare job_id sets to detect new openings automatically.

What if a company returns empty results? If a slug returns 0 jobs or a 404, it is logged and skipped cleanly — no crash, no charge, the run continues for remaining slugs.

Limitations

• department and employment_type are not exposed in the public JSON Feed (require authenticated API access)
• remote_type is inferred from title and location text (Teamtailor's public feed doesn't include a structured remote flag)
• Companies using custom career domains must pass the full domain, not a Teamtailor slug
• Some companies use Teamtailor's auth-required API instead of the public feed — these return 404 and are logged as failed

Output sample

{
  "title": "Senior Software Engineer",
  "company": "Hemnet",
  "location": "Stockholm, SE",
  "city": "Stockholm",
  "country": "SE",
  "remote_type": null,
  "seniority": "senior",
  "posted_at": "2026-05-28T13:06:16+02:00",
  "url": "https://hemnet.teamtailor.com/jobs/4567890-senior-software-engineer",
  "parse_confidence": 1.0,
  "warnings": [],
  "scraped_at": "2026-06-05T10:00:00+00:00"
}

Use with AI agents (MCP)

This actor is available via Apify's MCP server. Connect it to any MCP-compatible agent (Claude, n8n, Make) to pull live Nordic job data on demand — no code required.

https://mcp.apify.com/?tools=bovi/teamtailor-job-scraper

Vs. competitors

Feature	This actor	Generic job scrapers
parse_confidence quality score	Yes	No
Seniority enrichment (11 levels)	Yes	Rarely
Multi-company batch (1 run)	Yes	Rarely
Zero proxy / zero auth	Yes	Often needs proxy
Nordic/Teamtailor specific	Yes (native feed)	No (HTML scrape)
Price	$1.50/1K	$2–5/1K

Integrations

Built for Nordic talent-sourcing platforms and hiring-intel teams tracking open roles at Scandinavian tech companies — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

Not affiliated with Teamtailor

This actor scrapes publicly available career page data. It is not affiliated with, endorsed by, or sponsored by Teamtailor AB.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.