# Workday Jobs Api (`daftvader/workday-jobs-api`) Actor

- **URL**: https://apify.com/daftvader/workday-jobs-api.md
- **Developed by:** [Sam Towers](https://apify.com/daftvader) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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, SmartRecruiters & Workable Jobs

Collect normalized public job postings from Workday, SmartRecruiters, and Workable career sites in one dataset.

### Input

Provide a non-empty `companies` array. Each entry can be a supported career URL or an object with `value` and optional `source`, `tenant`, and `site` fields.

```json
{
  "companies": [
    "https://wd5.myworkdayjobs.com/example/Careers",
    {"value": "example", "source": "smartrecruiters"},
    {"value": "example", "source": "workable"}
  ],
  "filters": {
    "title": "engineer",
    "location": "Sydney",
    "remoteOnly": false,
    "postedAfter": "2026-01-01T00:00:00Z",
    "includeDescription": true,
    "maxResultsPerCompany": 200
  }
}
```

Supported filter fields are `title`, `location`, `remoteOnly`, `postedAfter`, `includeDescription`, and `maxResultsPerCompany` (1–10,000; default 200). Company names and domains can be resolved when they identify a supported public career source; successful name/domain resolutions are cached for later runs.

Optional `filters` fields are `title`, `location`, `remoteOnly`, `postedAfter` (ISO 8601), `includeDescription` (default `true`), and `maxResultsPerCompany` (default 200, maximum 10,000).

### Output and billing signals

Each dataset item is a normalized job with fields including `id`, `source`, `company`, `title`, `location`, `remote`, `posted_at`, `url`, `apply_url`, `description`, `employment_type`, and `department`. Results are deduplicated within a run, filtered before persistence, and capped separately for each company.

The run summary reports published jobs, newly resolved companies, and isolated company errors. A partial run can still publish successful companies.

### Supported sources

- Workday hosted career sites on `wd1`, `wd3`, `wd5`, and `wd103`.
- SmartRecruiters public career APIs.
- Workable public career APIs.

The Actor uses public HTTP endpoints and does not require browser automation or private credentials for these sources.

The implementation emits internal billing signals only after the corresponding action succeeds:

- `job-scraped` is emitted only after one filtered, deduplicated normalized record is successfully persisted.
- `tenant-resolved` is emitted only for a successful uncached name/domain resolution; explicit URLs, tenants, cached mappings, and failed resolutions do not emit it.

Provider or persistence failures are isolated per company and returned in the summary, preserving successful partial-run output and billing semantics.

# Actor input Schema

## `companies` (type: `array`):

Career URLs, company names/domains, or explicit provider objects.

## `filters` (type: `object`):

Optional title, location, remoteOnly, postedAfter, includeDescription and maxResultsPerCompany filters.

## Actor input object example

```json
{
  "companies": [
    "https://apply.workable.com/lucidya/"
  ]
}
```

# Actor output Schema

## `results` (type: `string`):

Normalized job records written to the Actor's default dataset.

# 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 = {
    "companies": [
        "https://apply.workable.com/lucidya/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("daftvader/workday-jobs-api").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 = { "companies": ["https://apply.workable.com/lucidya/"] }

# Run the Actor and wait for it to finish
run = client.actor("daftvader/workday-jobs-api").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 '{
  "companies": [
    "https://apply.workable.com/lucidya/"
  ]
}' |
apify call daftvader/workday-jobs-api --silent --output-dataset

```

## MCP server setup

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

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/pdEBx7YluIidoKsjL/builds/u1g0hIQmlaOreVrvB/openapi.json