# Dayforce Jobs Scraper (`jobsapi/dayforce-jobs-search-scraper`) Actor

Extracts normalized public Dayforce employer job postings from board URLs or exact posting URLs, including stable IDs, dates, locations, attributes, descriptions, structured salary fields and application links.

- **URL**: https://apify.com/jobsapi/dayforce-jobs-search-scraper.md
- **Developed by:** [Jobs API](https://apify.com/jobsapi) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.99 / 1,000 dayforce career roles

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## Dayforce Jobs Scraper

Extract public employer job postings from Dayforce career sites locally or on Apify. The Actor uses the anonymous public `JobFeeds` endpoint for board discovery and the public posting page's structured `__NEXT_DATA__` payload for detail enrichment. It does not log in, submit applications, access candidate data, use proxies, CAPTCHAs, or fingerprint spoofing.

### Modes

`search` discovers postings from one or more public board URLs. `single` fetches one exact `/jobs/{postingId}` URL. `multiple` fetches several exact posting URLs. Direct URLs are deduplicated by tenant, career-site code, and posting ID, and `maxItems` limits complete records.

```json
{
  "mode": "search",
  "startUrls": [
    { "url": "https://jobs.dayforcehcm.com/en-US/lssi/CANDIDATEPORTAL" }
  ],
  "searchText": "Supervisor",
  "maxItems": 3,
  "requestTimeoutSeconds": 15,
  "requestDelayMs": 500,
  "maxRequests": 100
}
```

Single and multiple examples:

```json
{ "mode": "single", "jobUrls": ["https://jobs.dayforcehcm.com/en-US/lssi/CANDIDATEPORTAL/jobs/1164"] }
```

```json
{
  "mode": "multiple",
  "jobUrls": [
    "https://jobs.dayforcehcm.com/en-US/lssi/CANDIDATEPORTAL/jobs/1164",
    "https://jobs.dayforcehcm.com/en-US/lssi/CANDIDATEPORTAL/jobs/2769"
  ]
}
```

### Dataset

Complete rows include employer and tenant identity, posting and requisition IDs, title/status/timestamps, evergreen/internal/remote flags, structured locations, job family/function, pay/employment/workplace attributes, salary ranges only when exposed by the feed, full source HTML and plain-text descriptions, separate header/body/footer text and HTML sections, source attributes, feed/site metadata, canonical/detail/listing URLs, source-backed apply URL when present, request receipts, field coverage, and quality metrics. The live LSSI detail page exposes benefits, essential functions, and position qualifications inside the published description; those sections remain source HTML and readable text rather than invented fields. Unavailable optional fields are omitted rather than emitted as nulls, empty arrays, empty strings, or invented placeholders.

Invalid inputs and public request/parser failures are stored in `RUN_DIAGNOSTICS` with sanitized error text and response receipts rather than mixed into the jobs dataset. `OUTPUT`, `OUTPUT_SUMMARY`, and `RUN_HEALTH` distinguish platform `status` (`SUCCEEDED` or `FAILED`) from dataset `resultStatus` (`COMPLETE`, `LIMITED`, `SKIPPED`, `DEFERRED`, `NO_DATA`, or `FAILED`). Complete jobs are staged until access classification is settled, then pushed sequentially; counts increase only after `pushData()` resolves. An explicit source denial discards staged rows and stops requests. Non-block failures after stored rows preserve them as `SUCCEEDED` / `LIMITED`; a fatal zero-row failure uses `Actor.fail()` and `FAILED` / `FAILED`. A clean empty result is `SUCCEEDED` / `NO_DATA`. HTTP 401/403/429/451 or a visible source-authored CAPTCHA, verification, or denial challenge is `SKIPPED`; HTTP 407 and no-response transport failures are `DEFERRED`, not source-block evidence. Diagnostics remain in key-value artifacts. No proxy, stealth, alternate identity, or fingerprint changes are used.

### Local development

```bash
npm install
npm test
npm run lint
apify validate-schema
apify run --purge --input-file INPUT.json
npm run validate:dataset -- storage
```

The same bounded input contract works locally and on Apify cloud. Automated tests use mocked requests; current source availability and a newly generated dataset remain unverified until a separately authorized run.

# Changelog

This Actor's version history is a separate document: https://apify.com/jobsapi/dayforce-jobs-search-scraper/changelog.md

# Actor input Schema

## `mode` (type: `string`):

Search a board, fetch one posting, or fetch multiple exact postings.

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

HTTPS jobs.dayforcehcm.com board URLs used by search mode. A direct /jobs/{postingId} URL is accepted for compatibility and is treated as a direct request.

## `jobUrls` (type: `array`):

HTTPS Dayforce posting URLs for single or multiple mode.

## `jobUrl` (type: `string`):

Convenience input for single mode.

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

Optional case-insensitive match against feed and enriched posting text.

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

Maximum unique complete job records to save.

## `requestTimeoutSeconds` (type: `integer`):

Timeout for each public feed or posting request.

## `requestDelayMs` (type: `integer`):

Small polite delay between public requests.

## `maxRequests` (type: `integer`):

Hard cap on logical public HTTP requests for this local run.

## Actor input object example

```json
{
  "mode": "search",
  "startUrls": [
    {
      "url": "https://jobs.dayforcehcm.com/en-US/lssi/CANDIDATEPORTAL"
    }
  ],
  "maxItems": 3,
  "requestTimeoutSeconds": 15,
  "requestDelayMs": 500,
  "maxRequests": 100
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `diagnostics` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("jobsapi/dayforce-jobs-search-scraper").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("jobsapi/dayforce-jobs-search-scraper").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 '{}' |
apify call jobsapi/dayforce-jobs-search-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jobsapi/dayforce-jobs-search-scraper"
        }
    }
}
```

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/OowQzD1TtMayN8Xrh/builds/vMMwLgBAWopUI6DmE/openapi.json