How to scrape Workday job postings legally (and why you shouldn't)
Workday tenant career pages are public. Scraping them is technically legal in most jurisdictions if you respect robots.txt and rate limits. Here's the right way - and why a managed API is almost always cheaper than DIY.
Dvir Atias
Founder, JobsPipe
“Scrape Workday” sits in an interesting legal grey zone. The tenant career pages at *.myworkdayjobs.com are publicly indexed, intended for public consumption, and explicitly listed in the parent company’s robots.txt as crawlable. So what’s the catch?
This post covers the legal posture, the technical reality, and why most teams that start with a DIY Workday scraper end up on a managed source within 6-12 months.
The legal picture (broadly)
In the US, the hiQ Labs v. LinkedIn case (2019, reaffirmed 2022) established that scraping publicly accessible data is not a violation of the Computer Fraud and Abuse Act. Workday job postings are publicly accessible. So far so good.
The asterisks:
- Workday’s TOS for the customer (the Workday tenant) covers the customer’s data, not yours-as-scraper.
- Some tenants set custom robots.txt rules that disallow crawling. Respect those.
- Rate limiting and respect of
Retry-Afterheaders matters legally and practically. - Republishing scraped postings without attribution may run into copyright on the description text.
None of this is legal advice. Talk to a lawyer if you’re shipping a commercial product.
The technical reality
Public Workday tenants expose a JSON feed at a predictable URL. You can POST a search filter and paginate through results. Sounds simple. The operational pain:
- Akamai bot management. A single static IP gets blocked within minutes once it crosses the rate threshold.
- Per-tenant URL variation. Different region prefixes, different tenant slugs.
- 10,000-result hard cap per search. To enumerate everything you slice by location/category.
- Tenant list maintenance. ~500 public tenants today, growing weekly as companies onboard Workday.
The build-vs-buy math
Running this in production typically takes one engineer ~3 months to ship and ~1 day/week ongoing. At loaded cost, that’s roughly $4,000-$6,000/month forever. JobsPipe’s Growth tier includes the entire Workday source for $199/month.
Most teams who go the DIY route do it because they want to learn the problem. Six months in, they migrate to a managed API and keep their original scraper as a fallback. That’s a sensible progression.
Skip the build - Workday + 30 other sources, one API.
Get a free API key
Frequently Asked Questions
Is it legal to scrape Workday job postings?
As general information rather than legal advice: Workday tenant career pages at myworkdayjobs.com are publicly accessible, and in the US the hiQ Labs v. LinkedIn case from 2019, reaffirmed in 2022, established that scraping publicly accessible data is not a Computer Fraud and Abuse Act violation. Asterisks apply around tenant robots.txt rules, rate limiting, and copyright on description text. Talk to a lawyer if you are shipping a commercial product.
What should I watch out for when scraping Workday job postings?
Four things, offered as general information and not legal advice. Workday's TOS with its tenant covers the customer's data, not you as a scraper. Some tenants set custom robots.txt rules that disallow crawling, and those should be respected. Rate limiting and honoring Retry-After headers matters both legally and practically. And republishing scraped postings without attribution may run into copyright on the description text.
How hard is it to run a Workday scraper in production?
Harder than the JSON feed makes it look. Public tenants expose a predictable feed you can POST search filters to, but Akamai bot management blocks a single static IP within minutes of crossing the rate threshold, tenant URLs vary by region prefix and slug, each search caps at 10,000 results, and the tenant list of ~500 public tenants grows weekly. That is roughly 3 months to ship and about 1 day per week ongoing.