Dayforce Jobs Scraper — Company Job Boards

What does Dayforce Jobs Scraper do?

Dayforce Jobs Scraper reads every open role on any employer's public Dayforce job board and returns it as structured data you can load straight into a spreadsheet, a database or a model. Employers that hire through Dayforce publish their roles at jobs.dayforcehcm.com/<language>/<client>/<board>; if a careers page's "Apply" button or job list leads there, this Actor reads it.

Give it the board's link, or the client and board from that link (acme/CANDIDATEPORTAL), and for each posting you get the title, every location with its city, state or province, postcode and country, the pay where the employer shows it, the employment type and job function where the employer sets them, the posted, closing and last-modified dates and a link to the posting — and, if you ask for it, the full text of the posting.

What makes it different:

• Three kinds of request, all counted. One request reads a board's settings — its employer's name and its languages. One request reads each 25 postings of its list. Then one request per posting you save reads that posting's own record, because Dayforce's list carries no pay. All of them go to the public JSON behind Dayforce's own job boards, at the Actor's default of 90 requests a minute. No HTML parsing, nothing to break when a board is restyled.
• Pay as the employer entered it. Dayforce holds pay as fields — a pay type, a hiring rate or a minimum and maximum hiring rate — in the posting's currency. Where the employer shows them, they come back as min, max, currency and period, with the fields' own labels kept in salary.raw. Where no rate is shown and the posting's text states a range, that range is read from the text. Nothing is estimated.
• Incremental mode. Put the Actor on a schedule and each run returns only postings that are new, changed, back again or gone. Unchanged postings are skipped, not charged, and cost no request for their records. Dayforce's list carries each posting's full text, so an edit to the text is seen without reading every record.
• One stable schema. Every row has every field, every time. Unknown is null, never a missing key, so nothing downstream breaks on a sparse posting. The schema is versioned (job.v1) and every Adderley Data jobs Actor uses it, so a Dayforce board, a Workday board and a job board sit in the same table.
• No personal data. A Dayforce board's settings name an accessibility contact and a correspondence address. This Actor never reads either, never touches the application side of a posting, and has nowhere to put a person. Contact details inside a posting's text are redacted by default.
• Bounded cost. You set a maximum number of results; the run stops there, and no record is requested for a posting that will not be saved. It also stops at the spending limit you set on the run in Apify.

What Dayforce data can you extract?

Field	What it holds
id	Stable across runs: source:market:sourceJobId. Use it as your primary key.
title	Job title as listed.
company.name	The hiring company, where the listing names one.
advertiser.name	The business that placed the listing — often a recruitment agency. Never a person.
location.raw	Location text as listed. Several locations are joined with |.
location.suburb	Suburb, when the listing states one.
location.city	City or area, when the listing states one.
location.region	State or region, e.g. VIC.
location.postcode	Postcode, when the source provides it.
location.country	ISO 3166-1 alpha-2 country code.
workArrangement	on_site, hybrid, remote or unknown.
employmentTypes	Normalised: full_time, part_time, contract, casual, temporary, internship, volunteer.
salary.raw	The salary text exactly as shown, or null when the listing shows none.
salary.min	Lower bound as a number, when the text contains one.
salary.max	Upper bound as a number. Equal to min for a single figure.
salary.currency	ISO 4217. Taken from the text, otherwise the market default.
salary.period	hour, day, week, month or year; null when the text does not say.
salary.includesSuper	true / false when the text says so ("plus super", "inc. super"); otherwise null.
classifications	The source's category and subcategory pairs.
teaser	The short summary shown on the results page.
bulletPoints	Selling points shown on the results page.
postedAt	When the listing was posted, ISO 8601 UTC.
updatedAt	The source's own last-modified time, ISO 8601 UTC. Published by ATS and API sources; null where the site does not show one.
expiresAt	Expiry, ISO 8601 UTC, where the source states one.
isPromoted	true for paid placements. A listing shown both promoted and organic is returned once.
url	Link to the listing.
description	Null unless requested. text, optional sanitised html, and contactsRedacted.
changeType	Incremental runs: NEW, UPDATED, REAPPEARED, EXPIRED (or UNCHANGED if you ask for those). Otherwise null.
firstSeenAt	Incremental runs: when this monitor first saw the listing.
contentHash	SHA-256 over the fields that define a change. Compare it to detect edits yourself.
scrapedAt	When this row was produced, ISO 8601 UTC.
source	Source key, e.g. seek.
market	Market key, e.g. au, nz.
sourceJobId	The source's own identifier for the listing.
company.sourceCompanyId	The source's identifier for the company, when exposed.
company.url	The company's page on the source site, when exposed.
advertiser.sourceAdvertiserId	The source's identifier for the advertiser.
schemaVersion	Always job.v1. Breaking changes ship as job.v2 in a new Actor version, never silently.

How Dayforce's fields fill the schema:

• company.name is the employer's name as its board's settings give it, e.g. Example Freight Pty Ltd. company.sourceCompanyId is Dayforce's client name (example-freight), and company.url the board.
• sourceJobId is the client and Dayforce's posting number (example-freight/50101), because a posting number is unique only within one employer. url is the posting's public page, https://jobs.dayforcehcm.com/<language>/<client>/<board>/jobs/<number>.
• location.raw is every location the posting lists, as Dayforce formats it, joined with |. city, region (the state or province code), postcode and country (an ISO code) are the first location's. A postcode is read only where the address writes it after the state code (Honolulu, HI 96815, USA); an address written with the state's name states none, and none is guessed. A posting whose only location is virtual reads Remote.
• workArrangement is remote for a posting whose only location is virtual. Where the employer sets Dayforce's Telecommute Percentage, 100 is remote, 0 on_site and anything between hybrid. Otherwise it is unknown: an office address alone does not say whether a role is hybrid.
• salary: min and max are the Hiring Min Rate and Hiring Max Rate, or the Hiring Rate as both; currency is the posting's currency code; period is hour for a pay type of Hourly and null for a pay type of Salary, which states no period. An hourly rate in the thousands is not read as pay. salary.raw keeps the fields as Dayforce labels them, e.g. Pay Type: Hourly · Hiring Min Rate: 48 · Hiring Max Rate: 55.
• employmentTypes comes from the words of Dayforce's Employment Indicator, which each employer names: "Full Time" gives full_time, "Seasonal Part Time" gives part_time and temporary. Words that name no type give an empty list.
• classifications holds the posting's Job Function, then its Job Family, each as a category, as the employer names them.
• postedAt is the posting's start date, expiresAt its closing date (null for a posting the employer marks as always open) and updatedAt the time Dayforce last recorded a change to it.
• market is always global: a Dayforce board is the employer's, not a country's.

How much does it cost to scrape Dayforce job boards?

You pay per posting saved to your dataset — $1.75 per 1,000 postings on Apify's Starter plan — plus $0.005 each time a run starts. There is no monthly rental.

Apify plan	Price	Per listing
Free	$1.75 per 1,000 listings	$0.00175
Starter (Bronze)	$1.75 per 1,000 listings	$0.00175
Scale (Silver)	$1.60 per 1,000 listings	$0.00160
Business (Gold)	$1.45 per 1,000 listings	$0.00145

Plus $0.005 per run start. Compute and proxy are included in these prices.

What you run	Cost (USD, Starter plan)
100 listings, one run	$0.18
1,000 listings, one run	$1.75
10,000 listings, one run	$17.50
50,000 listings, one run	$87.50
A daily incremental monitor finding about 150 new or changed listings a day, for a month	$8.03

Descriptions cost nothing extra here: the text arrives with the posting's record, which is requested for every saved posting anyway. Use incremental mode for anything you run more than once — after the first run you pay only for what changed.

How to scrape a Dayforce job board

1. Open the employer's Dayforce job board and copy its address. It looks like https://jobs.dayforcehcm.com/en-US/acme/CANDIDATEPORTAL: the language, then the client, then the board. A link to one posting on the board works too.
2. Open the Actor in Apify Console and go to the Input tab. Paste one link per line into Job boards. Up to 500 boards per run.
3. Optionally narrow the run: Search terms use Dayforce's own search box; Locations keep postings by place, country or Remote.
4. Set Maximum results. This is also your cost cap.
5. Press Start. When the run finishes, open the Output tab and export as JSON, CSV, Excel, XML or HTML, or read the dataset through the Apify API.

A posting that matches more than one search term is returned once.

Input

Field	Type	Default	What it does
boards	array	—	One entry per board: its link (https://jobs.dayforcehcm.com/en-US/acme/CANDIDATEPORTAL, or the link of any posting on it), a client and board code ("acme/CANDIDATEPORTAL"), or a client name alone, which is tried with the board code CANDIDATEPORTAL. Up to 500 boards per run; each costs one request for its settings, one per 25 postings of its list, and one per posting saved.
keywords	array	—	Each term is one search of each board with Dayforce's own search box, which matches titles and posting text. Leave empty for every posting.
locations	array	—	Keep postings with a location whose address, city or state or province code contains this text ("Denver", "Ontario", "VIC"), in this country ("Canada", "Australia", "US"), or, for "Remote", postings that list a virtual location. Two letters match a whole word only. Leave empty for all locations.
language	string	"en-US"	The language to read a board in when its link does not name one, as a code such as "en-US", "fr-CA" or "en-AU". A language the board does not offer is replaced with the board's first language.
maxResults	integer	100	The run stops once this many postings are saved. You are charged per posting saved, so this is also your cost cap. Each posting saved is also one request for its details.
includeDescription	boolean	false	On: the posting's full text comes back with each row, from the request already made for the posting's details, so it costs no extra requests. Off: listing fields only.
descriptionFormat	text, text_and_html	"text"	Plain text, or plain text plus sanitised HTML.
redactContacts	boolean	true	On by default: email addresses and phone numbers inside description text are replaced with [redacted]. This Actor never outputs recruiter names or contact fields.
incremental	boolean	false	Remember what earlier runs saw and save only postings that are new, changed or gone. Unchanged postings are skipped, not charged and cost no request for their details. Put the Actor on a schedule with this on.
stateKey	string	—	Optional name for this monitor, e.g. "competitor-operations". Runs with the same key share memory. Left empty, a key is derived from the boards and filters themselves.
emitExpired	boolean	true	Incremental mode only. When a complete run no longer finds a posting it saw before, save one row with changeType EXPIRED.
emitUnchanged	boolean	false	Incremental mode only. Saves (and charges for) every posting, labelled UNCHANGED where nothing moved.
proxyConfiguration	object	{"useApifyProxy":true}	Apify Proxy, automatic group, is the default and is what this Actor is tested with.
maxConcurrency	integer	4	Parallel requests. The default is deliberately modest.
maxRequestsPerMinute	integer	90	An upper bound on request rate across the whole run.

A typical input:

{
  "boards": [
    "https://jobs.dayforcehcm.com/en-US/ssagroup/CANDIDATEPORTAL"
  ],
  "maxResults": 100
}

The prefilled board, ssagroup, is one company's public Dayforce job board, used here only as an example of a public Dayforce board; it held 430 postings on 27 Sep 2026. This Actor is not affiliated with Dayforce or with that company. The prefill saves 20 postings, so a trial run makes 23 requests: the board's settings, its search token, its first 25 postings, and one for each posting's record.

Output

One row per posting. This is a synthetic example in the exact shape the Actor returns:

{
  "schemaVersion": "job.v1",
  "id": "dayforce:global:example-freight/50101",
  "source": "dayforce",
  "market": "global",
  "sourceJobId": "example-freight/50101",
  "url": "https://jobs.dayforcehcm.com/en-US/example-freight/CANDIDATEPORTAL/jobs/50101",
  "title": "Data Analyst",
  "company": {
    "name": "Example Freight Pty Ltd",
    "sourceCompanyId": "example-freight",
    "url": "https://jobs.dayforcehcm.com/en-US/example-freight/CANDIDATEPORTAL"
  },
  "advertiser": {
    "name": "Example Freight Pty Ltd",
    "sourceAdvertiserId": "example-freight"
  },
  "location": {
    "raw": "10 Sample St, Melbourne VIC 3000, Australia",
    "suburb": null,
    "city": "Melbourne",
    "region": "VIC",
    "postcode": "3000",
    "country": "AU"
  },
  "workArrangement": "unknown",
  "employmentTypes": [
    "full_time"
  ],
  "salary": {
    "raw": "Pay Type: Hourly · Hiring Min Rate: 48 · Hiring Max Rate: 55",
    "min": 48,
    "max": 55,
    "currency": "AUD",
    "period": "hour",
    "includesSuper": null
  },
  "classifications": [
    {
      "category": "Analytics",
      "subcategory": null
    },
    {
      "category": "Professional",
      "subcategory": null
    }
  ],
  "teaser": null,
  "bulletPoints": [],
  "postedAt": "2026-09-15T00:00:00.000Z",
  "updatedAt": "2026-09-16T01:02:03.456Z",
  "expiresAt": "2026-10-15T12:59:00.000Z",
  "isPromoted": false,
  "description": null,
  "changeType": "NEW",
  "firstSeenAt": "2026-09-27T21:30:12.000Z",
  "contentHash": "5c9c4badbe307fd203347267ef9406b97af04deb7db79d18fe92c97dc10e6537",
  "scrapedAt": "2026-09-27T21:30:12.000Z"
}

The Output tab has two table views: Overview (the fields most people want, flattened) and Changes (for incremental runs).

Incremental mode: monitor new roles across employers

Turn on Incremental mode and run the same input on a schedule — hourly, daily, weekly. The Actor keeps a small record of what it has seen and every row tells you what happened:

changeType	Meaning
NEW	First time this monitor has seen the posting
UPDATED	Seen before, and its title, locations or text has changed
REAPPEARED	Was reported as expired and is back
EXPIRED	Seen before and no longer on the board. One row, once
UNCHANGED	Only if you turn on Also save unchanged postings

How it behaves, so there are no surprises:

• The first run returns everything as NEW. From the second run you pay only for the difference.
• Change detection runs on the board's list — each posting's title, locations, virtual location and the words of its text — before any posting's record is requested. That is what keeps an unchanged posting free: no charge and no request. The cost is that an edit only to a posting's pay, employment type or job function is not reported as UPDATED, and neither is a new closing date. When a posting is saved for any other reason, its row carries the current pay.
• EXPIRED is only ever reported by a complete run. If a run hits your result cap or your spending limit, or a board cannot be read, nothing is declared expired — a posting on a board the run never read is not gone. In an EXPIRED row, company.name is the employer's name as last seen.
• A board's list is read 25 postings a page. If the list moves while it is being read — a posting added or taken down between two pages — the Actor reads it once more from the start; if it moves again, the run is treated as incomplete and nothing is declared expired from it.
• Runs share memory when they share a State key. Leave it empty and the key is derived from the boards and filters themselves, so the same input always continues the same monitor. Name it (competitor-operations) if you want to change filters later without starting again.
• A posting not seen for 45 days is forgotten.

Descriptions and contact details

Full descriptions are off by default. Turn on Include full descriptions and each row carries description.text (and sanitised description.html if you choose that format): the posting as Dayforce's board shows it, with the employer's standard opening and closing paragraphs around the posting's own text. Because the text comes with the posting's record, which is requested for every saved posting anyway, it costs no extra requests.

Postings sometimes contain a recruiter's email address or phone number. With Redact contact details on — the default — those are replaced with [redacted] and description.contactsRedacted is true; so is a personal profile address (linkedin.com/in/…). Neither description.text nor the optional HTML carries the address behind a link: the HTML keeps each link's words and drops its address, and drops images. The Actor never returns recruiter names or contact details as fields, under any setting: Dayforce's posting records name no recruiter or hiring manager, the board's own contact and correspondence details are never read, and the schema has nowhere to put a person. If your use case is contacting individuals, this is the wrong tool.

What people use it for

• Competitor and market hiring signals. Which employers are opening which roles, in which places, and how often — a daily monitor across a list of boards is one scheduled run.
• Pay-transparency datasets. Hiring rates across employers and roles, as numbers with their currency, and the employer's own fields kept beside them.
• Job aggregators and alert products. A clean feed of new postings from a curated list of employers, deduplicated and labelled by change.
• Sales and partnership research at company level. Growth signals from hiring, without collecting anything about the individuals involved.
• Research and teaching. A clean, repeatable dataset with a documented schema.

Using the API

Run it from code with the Apify client, using your own API token:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('adderleydata/dayforce-jobs-scraper').call({"boards":["https://jobs.dayforcehcm.com/en-US/ssagroup/CANDIDATEPORTAL"],"maxResults":100});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.length, items[0]?.salary);

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("adderleydata/dayforce-jobs-scraper").call(run_input={"boards":["https://jobs.dayforcehcm.com/en-US/ssagroup/CANDIDATEPORTAL"],"maxResults":100})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["title"], item["location"]["raw"], item["salary"]["raw"], item["postedAt"])

Schedules, webhooks and the Make, Zapier, n8n and Google Sheets integrations all work the way they do for any Apify Actor. The Actor runs with limited permissions and is priced per event, so AI agents can call it through Apify's MCP server as well.

Is it legal to scrape Dayforce job boards?

The Actor reads the public JSON that Dayforce's own job boards read, at a modest default rate, and returns facts about job postings. Like the board's own page, it first asks the board for the anonymous anti-forgery token Dayforce hands every visitor, with no account and no login, and sends it back with each search. It does not log in, does not solve CAPTCHAs, does not submit applications and does not collect personal information. If Dayforce ever answers with a challenge page, the run stops and says so rather than trying to get past it.

What you do with the data is your responsibility. Each employer's job text is its own copyright — analyse it, do not republish it. If your project touches personal information, privacy law applies to you wherever you are. This is general information, not legal advice.

Questions

Where do I find the board's link? Open any posting on the employer's careers page and follow it to Dayforce. The address starts https://jobs.dayforcehcm.com/, then a language (en-US), the client and the board. Paste the whole link.

Can I give just the employer's name? You can give Dayforce's client name alone (acme). It is tried with the board code CANDIDATEPORTAL, which both boards read when this Actor was built use; an employer whose board has another code is reported as not found, and its link is the way in.

A board I gave came back as "not found". Dayforce answers a client or board it does not have with "not found", and the run log names the board and says to copy its link. The other boards in the run are unaffected. A missing board is asked for once, not retried, and a run in which every board is missing finishes with an empty dataset and a message naming each one.

Which language are postings read in? The one in the board's link, or Language when the link names none. A board offers its own set of languages; one it does not offer is replaced with the board's first language.

Why does each saved posting cost a request? Dayforce's list carries titles, places, dates and text, but not pay, employment type or job function. Those are in each posting's own record, so the Actor asks for that record once for every posting it saves — and never for a posting a filter, the result cap or incremental mode leaves out. At the default of 90 requests a minute, 100 new postings take a little over a minute.

Why is workArrangement often unknown? Dayforce states a location, not a working pattern. The Actor says remote or hybrid only where the employer does — a virtual-only location, or a Telecommute Percentage — and unknown everywhere else.

Why is salary.period sometimes null when there are numbers? A pay type of Salary does not say whether the rate is yearly, monthly or per pay period, so the Actor leaves the period empty rather than guess. salary.raw shows exactly what the employer entered.

What if a posting is withdrawn during the run? If a posting disappears in the seconds between the board's list and the request for its record, it is saved with what the list said — title, places, dates and link — and the run log says so.

Can I get recruiter emails or phone numbers? No, by design.

How current is the data? It is read from Dayforce while your run is in progress. postedAt is the posting's start date and updatedAt Dayforce's last-modified time; scrapedAt records when the row was produced.

The field I need is not there. Open an issue on the Issues tab. Fields are added to the schema without breaking existing ones.

Support

Use the Issues tab on this page. We read it every day. Include the run ID and what you expected to see.

Other Adderley Data Actors

Every Actor in a vertical returns the same fields, so adding a source needs no new code on your side.

• Ashby Jobs Scraper — Company Job Boards — same job.v1 fields
• BambooHR Jobs Scraper — Company Job Boards — same job.v1 fields
• Breezy HR Jobs Scraper — Company Job Boards — same job.v1 fields
• Career Site Jobs Scraper — Greenhouse, Lever, Workday — same job.v1 fields
• Greenhouse Jobs Scraper — Company Job Boards — same job.v1 fields
• JazzHR Jobs Scraper — Company Job Boards — same job.v1 fields
• JobAdder Jobs Scraper — Agency and Employer Job Boards — same job.v1 fields
• Lever Jobs Scraper — Company Job Boards — same job.v1 fields
• Personio Jobs Scraper — Company Job Boards — same job.v1 fields
• Pinpoint Jobs Scraper — Company Job Boards — same job.v1 fields
• Recruitee Jobs Scraper — Company Job Boards — same job.v1 fields
• RemoteOK Jobs Scraper — Remote Job Feed — same job.v1 fields
• Rippling Jobs Scraper — Company Job Boards — same job.v1 fields
• Workable Jobs Scraper — Company Job Boards — same job.v1 fields
• Workday Jobs Scraper — Company Job Boards — same job.v1 fields

About

Made by Adderley Data, Melbourne — https://adderleydata.com. Not affiliated with, endorsed by or sponsored by Dayforce. Dayforce is a trade mark of its owner and is used here only to describe what this Actor reads.