From the blog · Page 6
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.
What "job closed or expired" means on Indeed (and what to do about it)
On Indeed, "job closed or expired" means the listing is no longer taking applications - either the employer closed it, or the posting ran out its visibility window. It is one combined status, so it does not tell you which happened, and it does not mean the role was filled. Here is how to tell the difference and what to do next.
Monster job posting API: the SOAP gateway, the search API, and who can actually use them
Two different products share the name. One posts jobs into Monster over a SOAP gateway on port 8443; the other reads postings out through a partner-issued token API. Every Monster developer surface, which way it moves data, how access works, and what the 2025 bankruptcy and sale to Bold changed.
Posting jobs to LinkedIn via API: what access actually requires in 2026
LinkedIn has a real job posting API. It is gated behind a Talent Solutions partnership, and the docs currently say new partnerships are closed. Here is the endpoint, the auth model, the quotas, and what to do if you actually wanted to read job data instead.
What happened to the Indeed Publisher API
For a decade the Indeed Publisher API was every developer's first stop for jobs data - free, public, XML. Indeed shut it down in 2023. What it was, why the strategic logic reversed, what replaced it (a display widget and a six-figure enterprise program), and what former users read Indeed postings with now.
The four Indeed partner APIs, explained
Indeed doesn't ship one API - it ships four, and all of them publish data into Indeed rather than reading it out. Job Sync, Indeed Apply, Disposition Sync, and Sponsored Jobs: what each does, who it's for, how to get access, and the one goal none of them serves.
Indeed API pricing: what it costs, and what's actually free
Indeed's official APIs are free to use and closed to most companies, the enterprise data program has no published price, and the unofficial providers meter you per result. What each path actually costs, why freshness drives the bill more than any per-call rate, and the line items that never make it into a quote.
Indeed API key: why there isn't one, and what to use instead
The Indeed publisher key stopped working in 2023 and was never replaced with a self-serve equivalent. How to recognise the tutorials that predate the shutdown, what credentials Indeed issues today and to whom, and the working path if your goal is reading Indeed job postings.
Unified API platforms: the two kinds, and which one job data needs
The unified API category contains two products that get confused constantly - one reads your customer's systems with their credentials, the other reads public data nobody has to authorize. They solve different problems, fail in different ways, and only one of them can answer 'who is hiring right now'. Which platforms sit where, and how to tell which you actually need.
Job aggregator sites: where each one actually gets its listings
Every aggregator looks the same from the outside and sources its listings completely differently underneath - XML feeds, ATS APIs, scraping, or paid inclusion. Which mechanism each major aggregator uses, why that decides freshness and coverage, and what it means if you are pulling listings programmatically rather than browsing them.