Workday Jobs Scraper: Any Careers Site, No API Key

Every open role from any Workday careers site, from the URL you already have. Titles, locations and links as clean JSON, no API key and no proxy. Workday is where large enterprises post: NVIDIA 2,000 open roles, Salesforce 1,478, Adobe 832.

What people use this for

Hiring data is not really about jobs. It is the earliest public signal a company gives that something changed, and it is why three different kinds of buyer end up on the same dataset:

• Sales and go-to-market. A company that opens six engineering roles this month is a company with new budget. Job postings say which team is growing and in which city, weeks before anything shows up in a funding announcement.
• Investors and market research. Headcount by function, tracked over time, across a whole portfolio or a whole sector. Every row carries the company, the team and the date, so a weekly run is a time series.
• Recruiting and talent. Where a competitor is hiring, which roles they have been trying to fill for months, and how fast a team is growing. Workday does not publish pay, so no row here claims to know it.

Run it once for a snapshot. Run it on a schedule and the same rows become a record of who started growing and when.

Company ids must be exact, and here is why

{ "boards": ["https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"] }

Domain guessing is deliberately switched off for workday. See the note below: a 200 from this API does not prove the company exists, so a guess could never be confirmed, and a confident wrong answer is worse than asking you for the id.

What makes workday different

• These are the biggest boards on any system. Measured 2026-08-01: NVIDIA 2,000 open roles, Salesforce 1,478, Adobe 832. Most large enterprises post here rather than on a startup ATS, so a jobs pipeline that stops at Greenhouse and Lever misses the companies people most want to watch.

• Workday caps the page size at 20 and answers 400 above it, undocumented, and that 400 reads as a malformed request rather than a paging problem. Measured: 20 returns 200, 50 is rejected.

• Workday's total lies after the first page. The real count arrives on page one and every page after it reports 0, so the obvious offset >= total loop is true immediately and stops at 40 of 2,000 postings, with no error and nothing in the log. This Actor keeps the first answer and stops only on an empty page.

• It needs the careers URL, not a company name, and that is not laziness. A Workday address carries three separate unknowns: the host label, the data-centre number (wd1 through wd12) and the career-site name. Guessing across them would mostly bill you for 404s, so this asks for the page you already have.

Filters that cost you nothing

{
  "boards": ["https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"],
  "titleKeywords": ["engineer"],
  "remoteOnly": true
}

Filtered rows are not charged. Keywords match as plain text, so c++ and node.js mean exactly that rather than being read as regular expressions.

What you get

Field
title	the role as the company wrote it
location	as published, not normalised
url	the public posting, ready to open
jobId	the ATS's own id, stable across runs
postedAtRelative	a phrase, not a date: "Posted Today", "Posted 30+ Days Ago". This source publishes no timestamp, and a date invented from that phrase would read as exact when it is not
company	what you asked for, echoed back
atsPlatform	which system it came from
boardToken	the board id used
boardTokenResolved	the board id derived from your URL
boardUrl	the public board this came from

Looking for an Indeed or Glassdoor API? There isn't one, and this is why you don't need it

Indeed has no public jobs API. Neither does Glassdoor, ZipRecruiter or LinkedIn Jobs, and all four block you at the edge. Measured from an ordinary residential address on 2026-08-01, with normal browser headers:

indeed.com/jobs          403      0 bytes
glassdoor.com/Job/...    403      0 bytes
ziprecruiter.com         403      0 bytes
upwork.com/nx/search     403      0 bytes

Zero bytes. Cloudflare rejects the request before it reaches an application, so there is nothing to parse and no proxy budget that fixes it.

But none of those four originate job data. They aggregate it from company career pages, and those pages run on systems like workday that publish a free, keyless, public API, because companies want their openings indexed. That API answered with real jobs from the same connection, in the same minute.

Going to the source is also fresher. An aggregator shows you its last crawl. This shows you the board.

Notes

• The source is a public API that companies publish deliberately. Nothing here is behind a login, a paywall or a bot wall.
• An empty board cannot be told apart from a wrong id on this system, and the message says so.
• Errors are per company. One bad token does not end the run, and error rows are not charged.