# Workday Jobs Scraper for Any List of Companies (`usta/workday-job-listings`) Actor

For recruiting-intelligence analysts and job aggregators: pull published jobs from public Workday career sites as one row each, with title, location, posted date, requisition number, full description and apply link.

- **URL**: https://apify.com/usta/workday-job-listings.md
- **Developed by:** [US Tech Automations](https://apify.com/usta) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 result rows

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Workday Career-Site Jobs for Any List of Companies

This workday scraper reads workday jobs from public career site jobs JSON for any list of companies that host careers on Workday.

Paste one or more Workday careers-page addresses. The run derives the host, tenant and site from each address, checks that host's robots.txt, then reads the same public jobs JSON the careers page itself loads. One published posting becomes one row.

### Input

| Field | What it does |
|---|---|
| **Workday careers-page URLs** | Addresses such as `https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite`. A locale segment like `en-US` is skipped. |
| **Search text** | Optional. Sent to Workday as `searchText` on the jobs list. |
| **Location contains** | Optional. Keep jobs whose location fields contain this text. |
| **Include description** | Default on. Fetches each job's public detail JSON for description, all locations, time type and posted date. |
| **Maximum rows** | Hard ceiling on rows returned, and therefore on the cost of the run. Default 50, maximum 10,000. |
| **Proxy configuration** | Optional Apify proxy. Off by default, including on a local run. |

### Pricing

**Pay per result. $0.003 per row. No start fee.**

Every dataset row bills from row one, including an error row for a site that 404s, is blocked, or whose robots.txt disallows the jobs path. A run that returns no rows costs nothing. **Maximum rows** is the spend cap.

### Output (one row per job)

One example row from a real local run on 2026-09-21 against `https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite` (description shortened here):

```json
{
  "company": "nvidia",
  "site": "NVIDIAExternalCareerSite",
  "title": "Senior Firmware Engineer – CSP Engagements",
  "location": "US, CA, Santa Clara",
  "locations": ["US, CA, Santa Clara"],
  "posted": "Posted Today",
  "posted_iso": "2026-09-20",
  "requisition_id": "JR1999599",
  "time_type": "Full time",
  "remote": null,
  "description": "NVIDIA is seeking a Senior Firmware Engineer to join our CSP Engagements team, focusing on system software for Datacenter products such as GB200. ...",
  "apply_url": "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite/job/US-CA-Santa-Clara/Senior-Firmware-Engineer---CSP-Engagements_JR1999599",
  "fetched_at": "2026-09-21T00:54:40Z"
}
```

| Field | What it holds |
|---|---|
| `company` | Tenant from the host (first label), e.g. `nvidia` |
| `site` | Career-site path name, e.g. `NVIDIAExternalCareerSite` |
| `title` | Job title |
| `location` | Primary location text from the detail when fetched, otherwise the list's location text |
| `locations` | All locations when the detail JSON lists them; otherwise `null` |
| `posted` | Workday's posted text (`Posted Today`, `Posted 2 Days Ago`, …) |
| `posted_iso` | Calendar date when it can be read (`startDate`, or derived from "Posted Today/Yesterday/N Days Ago"). `null` when it cannot, including `Posted 30+ Days Ago` |
| `requisition_id` | Requisition id from the list or detail |
| `time_type` | Full time / part time when the detail states it |
| `remote` | `true` when a location or remote field states remote; `null` when it does not |
| `description` | Job text with HTML stripped (when **Include description** is on) |
| `apply_url` | Public careers-page URL for that posting |
| `error` | `true` only on a failed site URL (missing site, block, robots disallow, not JSON) |
| `fetched_at` | When this run read the feed, in UTC |

### What this does not do

- It does not log in, use cookies, solve a CAPTCHA, or read applicant data. These feeds do not contain applicants.
- It does not scrape career-page HTML. Only the public `/wday/cxs/{tenant}/{site}/jobs` JSON and, when asked, each job's public detail JSON.
- It does not invent missing fields. Unreadable values are `null`.
- It does not discover a company's Workday URL from a name. You paste the careers address.
- It does not grant a licence to republish a company's jobs. Workday's own site terms still apply (see SOURCE\_TERMS.md).
- It does not search Indeed, LinkedIn, Greenhouse, Lever or Ashby.

### Limits

- `maxItems` is 1–10,000 (default 50). The run stops there even if a site holds more jobs. NVIDIA's public list reported `total` 2000 on the 2026-09-20 probe.
- This actor waits one second between HTTP calls to the same host. Checking robots.txt counts as a call. Each description is one extra GET.
- A 404, block, or robots disallow on one URL becomes one error row for that URL; other URLs in the same run still run.
- Email addresses and phone-number-shaped strings found in descriptions are replaced with `[redacted]`.

### Refunds and support

Refunds: if a run returns zero rows for a valid input, email operations@ustechautomations.com within 7 days and we refund that run. Support: same address, replies within 2 business days.

# Actor input Schema

## `startUrls` (type: `array`):

One or more public Workday careers URLs such as https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite. The HTML page is not scraped; only the public /wday/cxs/{tenant}/{site}/jobs JSON is read.

## `searchText` (type: `string`):

Optional. Sent to Workday as searchText on the jobs list. Leave blank for every published job on the site.

## `locationContains` (type: `string`):

Optional. Keep only jobs whose location fields contain this text (case-insensitive), e.g. Santa Clara or Remote.

## `includeDescription` (type: `boolean`):

When true (the default), fetch each job's public detail JSON for description, all locations, time type and posted date. When false, only the list fields are returned.

## `maxItems` (type: `integer`):

Hard ceiling on rows returned, and therefore on the cost of the run. Every row bills at the listed price from row one; there is no start fee. A blocked or missing site produces one error row for that URL.

## `proxyConfiguration` (type: `object`):

Optional Apify proxy. Leave off for a local run. Career-site jobs calls are ordinary HTTPS GET and POST requests.

## Actor input object example

```json
{
  "startUrls": [
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
  ],
  "includeDescription": true,
  "maxItems": 50,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `jobs` (type: `string`):

No description

## `csv` (type: `string`):

No description

## `report` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "startUrls": [
        "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
    ],
    "maxItems": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("usta/workday-job-listings").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "startUrls": ["https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"],
    "maxItems": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("usta/workday-job-listings").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "startUrls": [
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
  ],
  "maxItems": 50
}' |
apify call usta/workday-job-listings --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,usta/workday-job-listings"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/vfo0j9rTYIzOpx7bb/builds/prp8CDEaIq1yfg7V2/openapi.json