Workday Career Sites API - Find Companies Using Workday

Find the companies using Workday and every career site each one runs, returned as clean, machine-readable JSON. For any company you get its Workday tenant, its datacenter, the site slug, the public careers URL, the direct jobs API URL, and a live count of open roles. Give it a list of companies and it resolves them in seconds, or turn on Discover All and it enumerates Workday career sites in bulk to build a full Workday customer list.

The part that matters: it returns every career site a company runs, not just the main one. Large employers routinely operate separate boards for regions, subsidiaries, and university hiring. A single semiconductor company in testing returned 7 career sites; a design-software company returned 8. Tools that stop at the first board silently miss the rest.

This Actor reads only public career-site information published on Workday careers pages. It is not affiliated with, endorsed by, or connected to Workday, Inc.

What you get

• tenant - the company's Workday tenant label
• datacenter - which Workday datacenter hosts it (wd1, wd5, wd108 and so on). Not guessable, and required to build a working URL
• siteSlug - the individual career site identifier
• careersUrl - the public careers page, ready to open
• apiUrl - the direct machine-readable jobs endpoint for that site
• totalJobs - open roles on that site right now
• status and slugSource - verification outcome and how the site was resolved

What you do NOT get

• Individual job postings. This returns the career sites and the API URL for each; fetching the postings themselves is a separate step you control.
• Applicant or candidate data of any kind.
• Companies that are not on Workday. If an employer uses a different hiring platform, it will not appear.

Find the companies using Workday

Two ways to run it, depending on what you already know:

• You have a company in mind. Pass its name or domain and get back every Workday career site it runs, each with a direct jobs API URL and a live open-role count. Exact, and fast.
• You want the whole list. Turn on Discover All to enumerate Workday career sites in bulk from a public web index, then filter to the companies and boards you care about. This is how you build a Workday customer list or a Workday client list for sales and market research.

Use cases

• Sales and market research - build a list of companies using Workday, enriched with how many roles each has open, as a live buying signal.
• Recruiting data and sourcing tools - build a company-to-career-site map so your product can pull openings from any employer on demand.
• Job boards and aggregators - discover the employers worth ingesting, then hit each apiUrl directly instead of rendering career pages.
• Competitive intelligence - watch where a competitor is expanding by which regional boards grow.
• Data enrichment - resolve a company name to its Workday tenant and career-site URLs to append to your CRM or dataset.

When to use this Actor

	This Actor	Generic job scrapers	Manual lookup
Finds every career site a company runs	Yes	Usually just the first	Rarely
Returns a direct API URL per site	Yes	No	No
Resolves the datacenter	Yes	N/A	Trial and error
Bulk enumeration of companies using Workday	Yes	No	No
Speed	Seconds per company	Minutes	Manual

Rule of thumb: if you need the postings for one company you already know, use a job scraper. If you need to know which companies are on Workday and where their boards live, start here.

🔌 Integrations: turn Workday discovery into a recurring pipeline

This Actor is most useful as a step in a pipeline, not a one-off run. It resolves the career-site URLs; the tools below act on them.

• Tasks and Schedules. Save a run as a Task, then schedule it. Re-run a Workday customer list weekly (0 7 * * 1) to catch new companies and track how open-role counts move, or refresh a target-account list daily (0 6 * * *).
• Chain into job extraction. Feed each apiUrl straight into the Workday Careers API to pull the actual postings. Discovery here, extraction there.
• n8n, Make, and Zapier. Trigger downstream steps (enrich a CRM record, post to Slack, append a row) whenever a run finishes, using Apify's native connectors.
• Store the history (Supabase, BigQuery, a sheet). Push each run's dataset to your own store to build a time series of which companies run Workday and how their hiring changes.
• MCP and AI agents. Call it as a tool from Claude and other agents (see the MCP section below).
• Webhooks. Fire a webhook on run completion to kick off any of the above.

Pricing

Pay per career site returned. No per-run fee and no monthly minimum, so a single-company lookup costs a single site's worth. Current per-site pricing is shown on the Store page.

You are billed only for verified live sites unless you explicitly turn on includeInactive.

Input

Field	Type	Required	Default	Description
companies	array	No	["nvidia", "kla"]	Company names or domains to resolve, for example nvidia or cadence.com. Each is looked up independently and every career site it runs is returned.
discoverAll	boolean	No	false	Enumerate companies using Workday in bulk instead of resolving a named list.
maxResults	integer	No	100	Cap on companies processed in Discover All mode. One company can host several sites, so rows returned is usually higher.
verifyLive	boolean	No	true	Verify each site against its jobs endpoint and record its open-job count.
includeInactive	boolean	No	false	Also return sites that failed verification (dead or no_slug).
crawlDepth	integer	No	2	How many index snapshots to combine in Discover All mode. Higher finds more companies at the cost of a longer run.

Provide companies, or turn on discoverAll. An empty run exits cleanly with a message rather than an error.

Example input

{
  "companies": ["nvidia", "kla"],
  "verifyLive": true
}

Output

One dataset row per career site. A company that runs several boards produces several rows. Fields:

Field	Type	Description
resultType	string	career_site for a discovered site, error for a run-level problem
tenant	string	The company's Workday tenant label
companyName	string	The company as supplied in the input, when the row came from a named lookup
datacenter	string	The Workday datacenter hosting the tenant, for example wd1
hostKind	string	myworkdayjobs or myworkdaysite
siteSlug	string	Identifier of the individual career site
careersUrl	string	Public careers page, ready to open
apiUrl	string	Direct machine-readable jobs endpoint for that site
totalJobs	integer	Open roles on that site at the time of the run
status	string	live, dead, or no_slug
slugSource	string	How the slug was resolved, a confidence signal
discoveredAt	string	UTC timestamp of the row

Example output

{
  "resultType": "career_site",
  "tenant": "kla",
  "companyName": "kla",
  "datacenter": "wd1",
  "hostKind": "myworkdayjobs",
  "siteSlug": "Penang_Semicon",
  "careersUrl": "https://kla.wd1.myworkdayjobs.com/en-US/Penang_Semicon",
  "apiUrl": "https://kla.wd1.myworkdayjobs.com/wday/cxs/kla/Penang_Semicon/jobs",
  "totalJobs": 37,
  "status": "live",
  "slugSource": "robots",
  "discoveredAt": "2026-07-30T18:54:41+00:00"
}

How to get started

1. Open the Actor: View on Apify Store
2. Put one or more company names into Companies, or switch on Discover All Companies
3. Click Start
4. Read the results from the Output tab, or pull them from the dataset API

For a Python quick-start (uv) and copy-paste MCP install steps for Claude, Cursor, and ChatGPT, see the example repo on GitHub.

Run from the API

curl -X POST "https://api.apify.com/v2/acts/johnvc~workday-career-sites-api/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"companies":["nvidia","kla"],"verifyLive":true}'

🔌 Use this API from Claude (MCP)

Point any MCP client at the hosted Apify MCP server and this Actor becomes a tool your agent can call:

https://mcp.apify.com/?tools=actors,docs,johnvc/workday-career-sites-api

Works with Claude Code (free trial) and Claude Cowork (free trial). Ask it something like "find every Workday career site NVIDIA runs and tell me how many roles are open on each" and it will call this Actor and read the results back.

Apify MCP documentation: https://docs.apify.com/platform/integrations/mcp

🔗 Related Tools

• Workday Careers API - the natural next step. This Actor finds the career sites; that one extracts every job posting from a site's URL. Discovery then extraction.
• Google Jobs Scraper API (Pay Per Result) - pull job listings from Google Jobs when you want postings across employers, not one company's Workday boards.
• LinkedIn Jobs API - search job listings and salaries on LinkedIn, a complementary hiring-data source.
• LinkedIn Company API - firmographics for the companies you discover, useful for enriching a Workday customer list.

Compared with a single-company scraper such as crawlerbros/workday-jobs-scraper, which needs you to paste a Workday URL you already have, this Actor produces those URLs in the first place, then hands them off.

FAQ

What companies use Workday?

Thousands of large enterprises run their hiring on Workday, across technology, healthcare, retail, finance, and manufacturing. Turn on Discover All to enumerate them in bulk from a public web index, or pass a specific company name to confirm whether it runs Workday and get its career sites.

How do I build a list of companies using Workday?

Run the Actor in Discover All mode. It enumerates Workday career sites in bulk and returns one row per site with the company tenant, careers URL, and open-role count, which you can export as a Workday customer list or Workday client list for sales and research.

What is a Workday tenant?

It is the company's own label inside Workday, and the first part of its career-site hostname. For a URL like nvidia.wd5.myworkdayjobs.com, the tenant is nvidia. It is the field most people mean when they ask for a Workday tenant name.

Why does the datacenter matter?

Every Workday career site lives in a specific datacenter (wd1, wd5, wd108 and so on), and it is part of the URL. It cannot be derived from the company name, so without it you cannot build a working link or API call. This Actor resolves it for you.

Is this a Workday API or a web scraper?

Both, in effect. It behaves like an API: you send a company and get structured JSON back. Under the hood it discovers public career-site data the way a careful scraper would, but you never touch HTML or pagination. See the difference between an API and a web scraper if you are choosing between approaches.

Why does one company return several rows?

Because large employers run several career sites: a main board, plus separate ones for regions, subsidiaries, and university or graduate hiring. Each is a distinct site with its own URL and its own open roles, so each gets its own row.

Can I get the actual job postings?

Not from this Actor. Each row includes an apiUrl pointing at that site's jobs endpoint. Feed it to the Workday Careers API to page through the postings. This Actor's job is finding the boards.

What is myworkdayjobs.com?

It is the domain Workday hosts customer career sites on, in the form {tenant}.{datacenter}.myworkdayjobs.com. A live page there is a real employer career site; this Actor turns a company name into that URL.

Can I use this with the Apify API?

Yes. Start runs and read results through the Apify API, or use the run-sync-get-dataset-items endpoint shown above to get results in a single call.

Can I integrate this with other apps?

Yes. Use webhooks or the native connectors for Make and Zapier, plus n8n. Results land in a standard Apify dataset, so anything that reads a dataset works. See the Integrations section above.

Can I use this through an MCP server?

Yes. Point any MCP client at https://mcp.apify.com/?tools=actors,docs,johnvc/workday-career-sites-api and call it as a tool from an AI agent. See the MCP section above.

Do I need an API key?

No. There is nothing to sign up for and no third-party key to supply.

Can I schedule this?

Yes. Use Apify Schedules to re-run it on a cron, for example weekly, and track how a company's open-role counts move over time. See the Integrations section for cron examples.

Is it legal to scrape job data?

This Actor reads publicly available career-site information that employers publish for candidates to find. As with any data collection, review the terms of the sites you target and your own compliance requirements before running at scale.

How complete is bulk discovery?

Bulk mode is broad but not exhaustive. Some smaller employers are not represented in the underlying public index. If you have a specific company in mind, supply it in companies and it will be resolved directly, which is exact.

What does slugSource tell me?

How the site was identified. It is a confidence signal: sites resolved directly from the company's own published site list are the most reliable.

What happens if a company is not on Workday?

The run finishes cleanly and returns no rows for that company. You are not billed for a company that produces no sites.

n8n integration

Available as an n8n community node, n8n-nodes-workday-career-sites-api. In n8n: Settings, Community Nodes, install n8n-nodes-workday-career-sites-api, then use it in any workflow (it also works as an AI Agent tool).

Featured Tasks

Ready-to-run examples, each a saved configuration you can open and start in one click:

• Build a List of Companies Using Workday - enumerate companies on Workday in bulk.
• Build a Workday Customer List for Sales - a sales-ready list with open-role counts.
• Find Every Workday Career Site a Company Runs - all boards, not just the main one.
• Find a Company's Workday Careers URL - resolve a name to its careers URL.
• Get the Workday Tenant Name for a Company - the tenant and datacenter for any company.
• Get the Workday Jobs API URL for a Company - the direct jobs endpoint, ready to POST.
• Count Open Roles Across Workday Career Sites - hiring volume as a market signal.
• Find Accenture Workday Career Sites & Jobs URL
• Find Boeing Workday Career Sites & Jobs URL
• Find Barclays Workday Career Sites & Jobs URL

Last Updated: 2026.07.31