From the blog
How we build, what we learn, what we ship.
Posts about indexing public job postings at scale, salary parsing, and the systems that keep one universal JSON schema feeling small even as the source list keeps growing.
Payscale API: the compensation API you can read about but not sign up for
Payscale has exactly one documented API - Jobalyzer, a compensation-report service - and the docs never tell you how to get a key, because credentials come with a Payscale commercial relationship. Here is what the API actually does: OAuth client-credentials auth, report endpoints for pay, experience, skills and education impact, a Bayesian model over 60 million crowdsourced profiles, and metered per-report charges. And the ceilings that matter - eight countries, no bulk access, no employer dimension - plus the advertised-pay route when what you need is salary data as data.
Reed API: the UK jobs API you can actually get a key for
Indeed retired its Publisher API and LinkedIn sits behind partner programmes, but Reed.co.uk still hands out free API keys in minutes - for a real search endpoint over live UK postings. Here is how the Jobseeker API works: basic auth with the key as the username, the full filter surface, 100 results per page, and the details call you need for full descriptions. And where it stops - one board, one country, keyword-only filtering - plus what to reach for when that ceiling matters.
Careerjet API: a 90-country jobs API built for publishers, not pipelines
Careerjet runs localized job search in over 90 countries and hands out a free, documented search API - rare in this category. But every call must carry the IP and user agent of a real visitor, job links route through tracking redirects, descriptions arrive as sized fragments, and paging stops near result 1,100. Here is how the current v4 API actually works, why the GitHub client libraries no longer match it, and what to reach for when you need data rather than clicks.
Coresignal pricing: the full rate card, how credits burn, and what a job record costs
Coresignal is one of the few B2B data vendors with public prices: eight self-serve plans from $49 to $5,000 a month, all metered in one credit currency. The sticker tells you little until you know the burn - a job posting costs 1 credit, an employee or company profile 10 to 20, search previews bill per query, and monthly credits reset to zero. The full August 2026 rate card, the consumption rules, the 6.7x cliff between the Growth and Premium tiers, and where a flat jobs API buys ten times the postings for the same $49.
Levels.fyi API: what you get, how access works, and what it cannot answer
For years the official answer was no API, just embeds. That changed: Levels.fyi now sells a REST API, an MCP server and a CLI - behind a sales form, with no public pricing and no self-serve key. Here is what the official offering covers, what the free embeds and the scraper actors actually give you, and the market-wide question self-reported compensation data structurally cannot answer, with live advertised-pay numbers for contrast.
ESCO API: the EU's free skills and occupations API, explained for developers
The European Commission serves its entire skills and occupations classification - roughly 3,000 occupations, 14,000 skills, labels in 28 languages - through a free API with no key and no registration. How the search and resource endpoints actually work, the essential-skills graph that powers job matching, the version default that silently serves you an old revision, and an honest map of what reference data can never tell you about the live market.
ISIC codes: the industry classification behind global labour market data
ISCO-08 tells you what the worker does; ISIC tells you what the employer does. This is the industry half of that pair: how the Rev.4 hierarchy of 21 sections and 88 divisions works, the full section list, how ISIC relates to NACE, NAICS and SIC, what live job postings look like ranked by division - staffing agencies at number three is the interesting one - and how to filter postings by employer industry with a single query parameter.
Introducing Signals: stop checking whether a company started hiring
Most intent data infers interest - someone read an article, someone visited a pricing page. A job posting is different: the company declared the intent itself, dated it, and put budget behind it. The problem was never the data, it was having to go looking for it. Signals lets you save a search over millions of active postings and get an email, a Slack message or a signed webhook when a company newly matches, with an honest account of how fast it fires and what the dataset still does not know.
BLS API: how to pull US labor statistics, and where the survey data stops
The Bureau of Labor Statistics serves the most cited numbers in the US economy through a free JSON API - once you decode the series ID system. How to register a key, query CPS, CES, JOLTS and OEWS series, the real v1 vs v2 limits, and an honest map of what the API will never contain: job postings, company names, or anything fresher than the survey cycle.
Monthly changelog + engineering posts
One email a month. New sources, what we shipped, what we learned. Unsubscribe in one click.