Workday Jobs Scraper & API (Fast Edition)

Collect structured job postings from one or multiple public Workday career sites in a single run. Use the results for job-board feeds, recruiting research, hiring-data workflows, and scheduled employer snapshots—without a Workday login or API key.

The Actor uses a browser-free HTTP workflow against public Workday endpoints, paginates job listings, fetches available job details, and saves each matching posting to an Apify dataset.

What you get

• One or multiple Workday career-site URLs per run
• Pagination through available job listings
• Optional job-title and location filters
• Multiple locations retained as an ordered array
• Job title, tenant, country, time type, posting label, and post ID
• Canonical and locale-aware Workday job URLs
• Normalized descriptions plus detected responsibilities and qualifications
• Structured datasets available through the Apify API and exports
• Inputs that can be saved as an Apify Task and run on a schedule

Quick start

Use a public Workday job search page, not an individual job-detail URL.

{
  "startUrls": [
    { "url": "https://allens.wd3.myworkdayjobs.com/en-US/Allens" },
    { "url": "https://workday.wd5.myworkdayjobs.com/Workday" }
  ],
  "max_items": 100,
  "proxy_configuration": { "useApifyProxy": true },
  "keyword_filter": "engineer, manager",
  "location_filter": "Sydney, Remote"
}

Each URL is processed independently. In this example, the Actor can save up to 100 matching jobs from each career site.

Input reference

Field	Type	Required	Default	Behavior
startUrls	array	Yes	Example Workday URL	One or more public Workday job-search page URLs.
max_items	integer	No	100	Maximum matching jobs saved per URL. The Actor may scan more listings when filters are active.
proxy_configuration	object	No	Apify Proxy enabled	Connection settings for Workday requests. Residential proxies can help with stricter career sites.
keyword_filter	string	No	Empty	Comma-separated terms matched against job titles. Matching is case-insensitive and uses OR logic.
location_filter	string	No	Empty	Comma-separated terms matched against every listed location. Matching is case-insensitive and uses OR logic.

When both filters are set, a job must match the job-title filter and the location filter.

Existing integrations that still send the legacy start_url string remain accepted by the runtime, but new integrations should use startUrls.

Output

Every saved job contains the same 12 fields:

{
  "job_title": "Senior Data Engineer",
  "company": "example",
  "job_url": "https://example.wd5.myworkdayjobs.com/job/Berlin/Senior-Data-Engineer_R-123456",
  "job_url_ui": "https://example.wd5.myworkdayjobs.com/en-US/Careers/details/Senior-Data-Engineer_R-123456",
  "locations": ["Germany, Berlin", "Germany Remote"],
  "country": "Germany",
  "time_type": "Full Time",
  "posted_on": "Posted 2 Days Ago",
  "post_id": "R-123456",
  "description": "Normalized job description text...",
  "responsibilities": "Detected responsibilities text...",
  "qualifications": "Detected qualifications or requirements text..."
}

Field	Meaning
job_title	Job title supplied by Workday.
company	Workday tenant identifier derived from the career-site hostname.
job_url	Canonical public job URL returned or derived from Workday.
job_url_ui	Locale-aware Workday details URL when it can be constructed.
locations	One or more concrete job locations in source order.
country	Primary country descriptor supplied by Workday when available.
time_type	Workday employment time type, such as Full Time, when available.
posted_on	Workday's source posting label, which can be relative rather than an ISO date.
post_id	Workday requisition or posting identifier when available.
description	Normalized plain-text content before a detected responsibilities or qualifications section.
responsibilities	Detected responsibilities section; can be empty when the source has no recognized heading.
qualifications	Detected qualifications or requirements section; can be empty when the source has no recognized heading.

Results appear in the default dataset. Use the Job overview view for compact metadata and links, or the Job details view for descriptions and requirements.

API and exports

Run the Actor from your application with the standard Apify API:

curl -X POST \
  "https://api.apify.com/v2/acts/miladamirzadeh~workday-job-scraper-fast-edition/run-sync-get-dataset-items?token=<APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "startUrls": [{"url": "https://allens.wd3.myworkdayjobs.com/en-US/Allens"}],
    "max_items": 25
  }'

You can also use the generated Python, JavaScript, CLI, OpenAPI, and HTTP examples in the Actor's API tab.

Apify datasets can be exported in formats including JSON, CSV, Excel, XML, and HTML, or retrieved directly from the Dataset API.

Recurring workflows

Workday listings change continuously. Save a tested input as an Apify Task and schedule daily or weekly runs for:

• Employer career-page snapshots
• Job-board or recruiting-data ingestion
• Hiring-volume and location research
• Repeated collection for your own downstream comparison workflow

Each scheduled run creates an independent current dataset. This Actor does not itself compare runs, keep job history, emit only new jobs, or send change alerts.

Practical limitations

• Supports standard public Workday job-search pages; it does not support employee portals, SSO-protected pages, non-Workday ATS sites, or individual job-detail URLs as inputs.
• country is the primary country supplied by Workday. A multi-country posting can contain locations from more than one country while this field remains a single value.
• Workday employers structure description headings differently. responsibilities and qualifications are best-effort detected sections, not guaranteed fields.
• The Actor does not perform cross-run deduplication or change detection. Overlapping input career sites can produce overlapping results.
• Keyword filtering applies to job titles only; location filtering applies to location text only.
• Access can vary by Workday tenant and network route. Try an Apify Residential proxy if a public career site blocks other connections.

Pricing

The current Store pricing starts at $1 per 1,000 saved results. Filtering can reduce irrelevant output while max_items keeps the saved-result limit predictable per input URL. Check the Actor's Pricing tab for the current terms shown before each run.

Troubleshooting and support

If a run returns no jobs:

1. Confirm the input is a public Workday job-search page, not a job details page.
2. Temporarily remove both filters to rule out an overly narrow match.
3. Verify that the career site currently lists open jobs in a browser.
4. Try an Apify Residential proxy for a stricter tenant.

For support, open an Actor issue and include the target URL, proxy type, sanitized input, relevant log message, and expected behavior. Do not include API tokens or credentials.