Career Site Jobs Scraper — Greenhouse, Lever, Workday

What does Career Site Jobs Scraper do?

Career Site Jobs Scraper is one ATS jobs API for company career sites. Give it a list of companies (job-board links, domains or plain names) and it returns every open role at each of them as JSON, CSV, Excel or a Google Sheet, in one schema, from fifteen applicant tracking systems: Greenhouse, Lever, Ashby, Workday, Recruitee, Breezy HR, Rippling, Workable, BambooHR, Personio, JazzHR, Pinpoint, Dayforce, JobAdder and Employment Hero.

• Up to 500 companies in one run, up to 200 of them as names or domains, filtered by title keywords, locations and, where the source states them, departments and publication dates.
• Run it as a daily monitor. Each scheduled run returns only the postings that are new, changed or gone since the last one, and unchanged postings are not charged.
• Call it as an API. One HTTP request runs it and returns the rows as JSON or CSV (the command is under Questions). Python, JavaScript, Make, Zapier, n8n and AI agents through Apify's MCP server can call it too.

Most companies do not host their own job listings: their careers page is a front for an applicant tracking system (ATS). This Actor reads each ATS where it publishes a company's jobs for its careers page: a public API or feed on thirteen of them, the careers page itself on JazzHR and JobAdder.

Each entry in the list can be a job-board link (https://jobs.lever.co/acme), a source and a board name (lever:acme), a company domain (acme.com) or just a company name (Acme Robotics). For every company it finds, you get each posting's title, department, location with its country, workplace type, employment type, pay range where stated, posted and updated dates and a link, and, if you ask for it, the full text.

What makes it different:

• Fifteen ATSs, one list, one schema. Greenhouse, Lever, Ashby, Workday, Recruitee, Breezy HR, Rippling, Workable, BambooHR, Personio, JazzHR, Pinpoint, Dayforce, JobAdder and Employment Hero boards sit in one dataset, each row with its source. The same fields Adderley Data's single-source Actors return, so nothing downstream changes when a company moves ATS.
• Names and domains are looked up for you. A company name or domain is tried as a board name on the nine ATSs that can be asked by name: Greenhouse, Lever, Ashby, Recruitee, Breezy HR, Rippling, BambooHR, Personio and JazzHR. A source that has no board by that name answers "not found", plainly, once: that is an answer, not an error, it is never retried and it is never charged. A company that turns up nowhere is named in the run's log and summary.
• Six sources by link. Boards on Workday, Workable, Pinpoint, Dayforce, JobAdder and Employment Hero are never guessed from a name. Give the board link (acme.wd5.myworkdayjobs.com/External, apply.workable.com/acme, acme.pinpointhq.com, jobs.dayforcehcm.com/en-US/acme/CANDIDATEPORTAL, clientapps.jobadder.com/12345/acme-recruitment, employmenthero.com/jobs/organisations/acme-health) or pin the source (workable:acme), and the Actor reads it exactly as Adderley Data's Actor for that source does, pay and dates included. Questions says why each one needs its link.
• 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 and not charged.
• One stable schema. Every row has every field, every time. Unknown is null, never a missing key. The schema is versioned (job.v1).
• No personal data. The Actor reads no recruiter fields from any source and has nowhere to put one. Contact details inside posting text are redacted by default.
• Bounded cost. You set a maximum number of results; the run stops there. It also stops at the spending limit you set on the run in Apify.

What data can you extract from company career sites?

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 the sources fill the schema:

• source names the ATS: greenhouse, lever, ashby, workday, recruitee, breezy, rippling, workable, bamboohr, personio, jazzhr, pinpoint, dayforce, jobadder or employmenthero. id is source:market:sourceJobId, stable from run to run.
• company.sourceCompanyId is the company's board name on that ATS — the part you would put after lever: to read that board again directly.
• JobAdder careers pages belong mostly to recruitment agencies, whose ads are for their clients. On a JobAdder row the business whose careers page it is is the advertiser — advertiser.sourceAdvertiserId is its account and page name, 12345/acme-recruitment — and company is null, as on Adderley Data's JobAdder Actor. No hiring company is guessed.
• postedAt is the source's own publication date. updatedAt is the source's last-modified time where it publishes one (Greenhouse, Ashby, Recruitee, Dayforce); elsewhere it is null.
• salary holds the pay the posting states, as numbers with a currency and a period, and the words it was stated in. Nothing is estimated and currencies are never converted.
• Workday, Rippling, BambooHR, JazzHR, Pinpoint and Dayforce boards list less than a row holds, so each saved posting's own record or page is read for what the list leaves out — on most of them its posted date, its pay or both — whether or not you ask for its text. That is part of the price of a row, not an extra charge.
• A JobAdder careers page shows no pay: a pay range is read from an ad's own text, so on JobAdder rows salary is filled only when descriptions are on.
• Personio boards are read in English. Personio keeps a job's text per language, so a job its company wrote in another language only — German, on many Personio boards — comes with its facts and description set to null; the Personio Jobs Scraper reads other languages.
• Each source's own details — how Workday states places, how Rippling lists several pay ranges, how Breezy HR states a currency — are exactly those of Adderley Data's Actor for that source, and are described in its README.

How much does it cost to scrape company career sites?

You pay per posting saved to your dataset — $2.00 per 1,000 postings on Apify's Starter plan — plus $0.005 each time a run starts. There is no monthly rental. Looking a company up costs nothing per result: a source that has no board by the name asked is never charged.

Apify plan	Price	Per listing
Free	$2.00 per 1,000 listings	$0.00200
Starter (Bronze)	$2.00 per 1,000 listings	$0.00200
Scale (Silver)	$1.80 per 1,000 listings	$0.00180
Business (Gold)	$1.60 per 1,000 listings	$0.00160

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.21
1,000 listings, one run	$2.00
10,000 listings, one run	$20.00
50,000 listings, one run	$100.00
A daily incremental monitor finding about 150 new or changed listings a day, for a month	$9.15

Use incremental mode for anything you run more than once — after the first run you pay only for what changed.

How to scrape the careers pages of a list of companies

1. Collect your companies. The fastest entry is a board link: open the company's careers page, click any job, and copy the address it opens — boards.greenhouse.io/…, jobs.lever.co/…, jobs.ashbyhq.com/…, ….myworkdayjobs.com/…, ….recruitee.com, ….breezy.hr, ats.rippling.com/…, apply.workable.com/…, ….bamboohr.com, ….jobs.personio.de, ….applytojob.com, ….pinpointhq.com, jobs.dayforcehcm.com/…, clientapps.jobadder.com/… or employmenthero.com/jobs/organisations/…. A domain or a plain company name works too, except for a board on the six sources that always need their link — Workday, Workable, Pinpoint, Dayforce, JobAdder and Employment Hero; see Questions for how a name is looked up.
2. Open the Actor in Apify Console and go to the Input tab. Paste one company per line into Companies. Up to 500 per run, of which up to 200 names or domains.
3. Optionally filter: Title keywords, Locations, Departments, Published within (days).
4. Set Maximum results. This is also your cost cap, across all companies together.
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. The run's summary (the RUN_SUMMARY record) lists what each company was found as.

A posting found twice — the same company given as a link and as a name — is returned once.

Input

Field	Type	Default	What it does
companies	array	—	One entry per company, in any of these forms: a job-board link on any of fifteen sources — boards.greenhouse.io/acme, jobs.lever.co/acme, jobs.ashbyhq.com/acme, acme.wd5.myworkdayjobs.com/External, acme.recruitee.com, acme.breezy.hr, ats.rippling.com/acme, apply.workable.com/acme, acme.bamboohr.com/careers, acme.jobs.personio.de, acme.applytojob.com/apply, acme.pinpointhq.com, jobs.dayforcehcm.com/en-US/acme/CANDIDATEPORTAL, clientapps.jobadder.com/12345/acme-recruitment or employmenthero.com/jobs/organisations/acme-health (read exactly as given); a source and a board name such as "lever:acme" (read on that source only); a company domain such as acme.com, or a careers-page link on it (its name is taken from the domain); or a company name such as "Acme Robotics". A domain or a name is looked up as a board name on Greenhouse, Lever, Ashby, Recruitee, Breezy HR, Rippling, BambooHR, Personio and JazzHR. Workday, Workable, Pinpoint, Dayforce, JobAdder and Employment Hero boards always need their link or a pin such as "workable:acme". Up to 500 entries per run, of which up to 200 domains or names.
keywords	array	—	Keep postings whose title contains every word of any keyword, in any order — "engineer data" matches "Senior Data Engineer". On Workday and Dayforce boards each keyword is a search on the board itself. Leave empty for all titles.
locations	array	—	Keep postings whose location contains this text, e.g. "Melbourne", "Canada", "Remote". Leave empty for all locations.
departments	array	—	Keep postings in a department whose name contains this text, e.g. "Engineering" — on JobAdder the posting's category, on Employment Hero its team. Dayforce boards list no department, so this filter is not applied to them. Leave empty for all departments.
postedWithinDays	integer	—	Keep postings first published in the last N days. Rippling, BambooHR, JazzHR and Pinpoint boards list no dates, so this filter is not applied to them; Workday boards state a posting's age only up to 30 days, so a longer window reads every Workday posting. Leave empty for any time.
maxResults	integer	100	The run stops once this many postings are saved, across all companies. You are charged per posting saved, so this is also your cost cap.
includeDescription	boolean	false	On: the full posting text comes back with each row. On Greenhouse, Lever, Ashby, Recruitee, Workable, Personio, Pinpoint and Employment Hero it arrives with the board itself, and on Workday, Rippling, BambooHR, JazzHR and Dayforce with the posting's own record, which is read anyway: no extra request. On Breezy HR and JobAdder it costs one request per posting saved. Personio text is read in English. 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, phone numbers and personal profile links 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 and not charged. Put the Actor on a schedule with this on.
stateKey	string	—	Optional name for this monitor, e.g. "competitor-hiring". Runs with the same key share memory. Left empty, a key is derived from the companies 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, all sources together. Workable boards are read at most one request every six seconds and Employment Hero boards one every ten, whatever this says.

A typical input:

{
  "companies": [
    "Ashby",
    "Rippling",
    "https://boards.greenhouse.io/greenhouse"
  ],
  "maxResults": 100
}

Output

One row per posting. This is a synthetic example in the exact shape the Actor returns — a Greenhouse board found from the name "Example Freight":

{
  "schemaVersion": "job.v1",
  "id": "greenhouse:global:7000101",
  "source": "greenhouse",
  "market": "global",
  "sourceJobId": "7000101",
  "url": "https://job-boards.greenhouse.io/example-freight/jobs/7000101?gh_jid=7000101",
  "title": "Data Analyst",
  "company": {
    "name": "Example Freight Co",
    "sourceCompanyId": "example-freight",
    "url": "https://job-boards.greenhouse.io/example-freight"
  },
  "advertiser": {
    "name": "Example Freight Co",
    "sourceAdvertiserId": "example-freight"
  },
  "location": {
    "raw": "Melbourne, Victoria, Australia",
    "suburb": null,
    "city": "Melbourne",
    "region": "Victoria",
    "postcode": null,
    "country": "AU"
  },
  "workArrangement": "unknown",
  "employmentTypes": [],
  "salary": {
    "raw": "The salary range for this role is A$95,000 – A$110,000 per year plus super.",
    "min": 95000,
    "max": 110000,
    "currency": "AUD",
    "period": "year",
    "includesSuper": false
  },
  "classifications": [
    {
      "category": "Data",
      "subcategory": null
    },
    {
      "category": "Analytics",
      "subcategory": null
    }
  ],
  "teaser": null,
  "bulletPoints": [],
  "postedAt": "2026-09-20T22:14:05.000Z",
  "updatedAt": "2026-09-21T03:02:11.000Z",
  "expiresAt": null,
  "isPromoted": false,
  "description": null,
  "changeType": "NEW",
  "firstSeenAt": "2026-09-21T19:30:12.000Z",
  "contentHash": "1aa33a7fa1171769f261473be1b6a98c450af56dde37f9c785a47fb084b189ce",
  "scrapedAt": "2026-09-21T19: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 hiring across a list of companies

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 something the source reports about it has changed
REAPPEARED	Was reported as expired and is back
EXPIRED	Seen before and no longer on the company's 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.
• What counts as a change is the source's own: on Greenhouse, Ashby and Recruitee an edit anywhere in a posting moves its last-modified time, and that is reported; on Workable, Personio, Pinpoint and Dayforce an edit to a posting's text or to any fact its board lists is reported; on Employment Hero an edit to any fact its list shows, pay included, is reported, and an edit only to a posting's text is not; on Workday, Rippling, BambooHR, JazzHR and JobAdder, change is judged from what the board's list shows (title, place, department), so an edit only to a posting's text or pay is not reported.
• 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 source answering "no board by that name" is an answer, so it does not make a run incomplete — and a board that was found before and has now gone reports its postings as expired, which is what happened.
• For a monitor, prefer board links over names: a link is read exactly as given every run, while a name is looked up again each time.
• Runs share memory when they share a State key. Leave it empty and the key is derived from the companies and filters themselves, so the same input always continues the same monitor.
• 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). On Greenhouse, Lever, Ashby, Recruitee, Workable, Personio, Pinpoint and Employment Hero the text arrives with the board itself and costs no extra request; on Workday, Rippling, BambooHR, JazzHR and Dayforce it comes with the posting's own record, which is read for every saved posting anyway; on Breezy HR and JobAdder it costs one request per posting saved. Breezy HR turns away some of those requests with HTTP 403 — between one in ten and one in five in our runs on 12 and 13 October 2026 — and the Actor takes that as the answer: it does not ask again, and saves that posting with the facts from the board's list and without its text. The run summary counts them under adapter.sources.breezy.postingPagesRefused.

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/…). The optional 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: it reads no such fields from any source, and the schema has nowhere to put one. If your use case is contacting individuals, this is the wrong tool.

What people use it for

• Competitor and market hiring signals. Which companies are opening which roles, in which departments and countries — a daily monitor across a list of companies is one scheduled run, whatever ATS each one uses.
• Job boards and alert products. A clean feed of new postings from a curated list of employers, deduplicated and labelled by change.
• Pay-transparency datasets. Stated ranges across companies and roles, as numbers with their currency and period, and the words they were stated in.
• 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/career-site-jobs-scraper').call({"companies":["Ashby","Rippling","https://boards.greenhouse.io/greenhouse"],"maxResults":100});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.length, items[0]?.source, items[0]?.title);

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("adderleydata/career-site-jobs-scraper").call(run_input={"companies":["Ashby","Rippling","https://boards.greenhouse.io/greenhouse"],"maxResults":100})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["source"], item["company"]["name"], item["title"], item["location"]["country"])

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 company career sites?

The Actor reads the public job boards that Greenhouse, Lever, Ashby, Workday, Recruitee, Breezy HR, Rippling, Workable, BambooHR, Personio, JazzHR, Pinpoint, Dayforce, JobAdder and Employment Hero serve for their customers' own careers pages — with no login, no key and no rate tricks — at a modest default rate, and returns facts about job postings. It does not log in, does not solve CAPTCHAs, and does not collect personal information. It does not fetch the companies' own websites: a domain is used only to make a board name.

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

Questions

Is there one API for jobs from every ATS? No ATS publishes another ATS's jobs, and each one's feed has its own shape, its own names for the same facts and its own way of paging. This Actor is that single API for fifteen of them, in one schema. One request runs it and returns the rows:

curl -X POST "https://api.apify.com/v2/acts/adderleydata~career-site-jobs-scraper/run-sync-get-dataset-items?format=json" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"companies":["Ashby","Rippling","https://boards.greenhouse.io/greenhouse"],"maxResults":100}'

That call waits for the run, so it suits runs that finish inside the 300 seconds Apify allows it; for bigger runs, start the run and read its dataset when it finishes, as Using the API shows. format=csv returns CSV instead of JSON.

How do I get jobs from company career sites into Google Sheets? Three ways, none of them code. Export the run's dataset as CSV or Excel from the Output tab and open it in Google Sheets. Or, on the Actor's Integrations tab, add Upload results to GDrive: after each successful run a file lands in the Apify Uploads folder of your Google Drive, in the format you choose. Or use Zapier, Make or n8n to add each run's rows to a sheet. With incremental mode on, a daily run carries only that day's changes.

How do I monitor new jobs at a list of companies? Turn on Incremental mode, save the list as a task and give the task a daily schedule under Schedules. Each run returns only the postings that are new, changed, back again or gone since the last run, each labelled in changeType, and unchanged postings are skipped and not charged. Give links or pins rather than names for a monitor you rely on: a link reads the same board every time.

How does it find a company from its name? It makes a board name from what you give it — Acme Robotics Pty Ltd becomes acmerobotics and acme-robotics (legal words like Pty, Ltd, Inc and GmbH are dropped); careers.acme.com.au becomes acme — and asks Greenhouse, Lever, Ashby, Recruitee, Breezy HR, Rippling, BambooHR, Personio and JazzHR whether they have a board by that name. Every source that has one is read. That is up to eighteen small requests per name, none of them charged. A Recruitee board that holds only Recruitee's own sample postings is treated as not found when a name is looked up: Recruitee's trial accounts under large brands' names hold nothing else.

Can a name match the wrong company? Yes. A board name is only a name, and a common word can belong to different companies on different sources: in a check on 25 September 2026, "jobs" matched boards on Ashby, Recruitee and Breezy HR. Every row carries its source and company.name, and the run summary lists every board each name matched. When you need certainty, give the board link, or pin the source: lever:acme reads Lever's acme board and nothing else.

A company came back as "No job board found". None of the nine sources asked has a board under the names tried. The company may use a different board name (open any job on its careers page and copy the link), a board on one of the six sources that always need their link — Workday, Workable, Pinpoint, Dayforce, JobAdder or Employment Hero — or an ATS this Actor does not read. The run log and summary name each such company; the other companies in the run are unaffected.

Why do Workday, Workable, Pinpoint, Dayforce, JobAdder and Employment Hero need a link? Each for its own reason:

• Workday: a board is a tenant, a numbered data centre and a site name — acme.wd5.myworkdayjobs.com/External — and nothing public maps a company's name to those three.
• Workable: its servers refuse an address that sends more than a handful of requests in quick succession, and looking up a list of names there would pass that within the first few companies. Workable boards given by link are read one every six seconds at most, whatever the run's rate. A board Workable refuses with a 429 (too many requests) is waited for — as long as Workable asks, or 30 seconds — and asked again from the same address, twice at most; the Actor never switches address to get round the limit.
• Pinpoint: some Pinpoint sites named after well-known brands are demonstrations that list Pinpoint's own made-up sample jobs, so a name looked up there could return, and charge you for, postings no company has.
• Dayforce: a board is an employer's client name and a board name — jobs.dayforcehcm.com/en-US/acme/CANDIDATEPORTAL — and nothing public maps a company's name to both.
• JobAdder: a careers page is named by the business's JobAdder account number as well as a name — clientapps.jobadder.com/12345/acme-recruitment — and no public page maps a company to the number. A link copied after a search in the page's own keyword box ends in ?keyword=…; that search is not applied, the page is read whole and narrowed by your own filters, and the run's log and status message say so. Put the words in Title keywords instead.
• Employment Hero: a careers page's name is often the company's with a few characters Employment Hero adds (acme-health-xhp08), so a name seldom matches, and Employment Hero asks for ten seconds between requests, so every miss would cost ten seconds. Employment Hero boards are read one request every ten seconds whatever the run's rate. A request Employment Hero refuses with a 429 is waited for — as long as it asks, up to two minutes, or a minute when it does not say — and asked again from the same address, twice at most.

A link or a pin (workable:acme, pinpoint:acme, dayforce:acme/CANDIDATEPORTAL, jobadder:12345/acme-recruitment, employmenthero:acme-health) reads the board directly, as it does on every source.

Does it read the company's own careers page? No. A careers page's job list is drawn by the ATS, so the Actor reads the ATS directly; a domain is only used to make a board name. A board found only on a careers page would have to be found again on every run, and a page redesign would read as every posting expiring.

Is postedWithinDays applied everywhere? On every source but Rippling, BambooHR, JazzHR and Pinpoint, whose boards list no dates. Their rows still carry postedAt where the posting's own record states it, so filter on it in your dataset. Workday states a posting's age only up to 30 days, so a window longer than 30 days reads every Workday posting.

Is departments applied everywhere? On every source but Dayforce, whose job list names no department: a Dayforce posting's category is in its own record, which is read only once the posting has been chosen for your dataset, so every posting on a Dayforce board is returned whatever the filter says. Filter on classifications in your dataset instead. On JobAdder a department is the posting's category or sub-category, and on Employment Hero its team.

Why is a board I gave "not found"? The source says it has no board by that name — a typo, a board the company has closed or made private (BambooHR and JazzHR say so for an expired or inactive account, and BambooHR for a careers site behind its sign-in page), a Lever or Rippling name with different capitals (those two are case-sensitive), or a Dayforce employer whose board has a code other than CANDIDATEPORTAL, which a pin such as dayforce:acme assumes (give its link). It is asked once, not retried, and named in the log.

Does it need a login or an API key? No. Every job board it reads is public.

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

How current is the data? It is read from each source while your run is in progress. postedAt is the source's publication date; scrapedAt records when the row was produced.

The ATS I need is not here. Open an issue on the Issues tab and name it. Sources are added without breaking existing fields.

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
• Dayforce Jobs Scraper — Company Job Boards — same job.v1 fields
• Employment Hero Jobs Scraper — Employer Careers Pages — 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 Job Board API & Jobs Scraper — 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 Job Board API & Jobs Scraper — same job.v1 fields
• Workable Job Board API & Jobs Scraper — 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 Greenhouse, Lever, Ashby, Workday, Recruitee, Breezy HR, Rippling, Workable, BambooHR, Personio, JazzHR, Pinpoint, Dayforce, JobAdder, Employment Hero or any company whose job board it reads. Their names are trade marks of their owners and are used here only to describe what this Actor reads.