ATS Hiring Signals

Extract public job postings from Greenhouse, Lever, Ashby, SmartRecruiters, Recruitee, Workable, and Personio. Use one consistent dataset for recruitment research, sales intelligence, and scheduled hiring monitoring.

Quick start

1. Paste company ATS career-board URLs into Career board URLs.
2. Optionally add title/department keywords, such as sales or marketing.
3. Run the Actor and export results to JSON, CSV, or Excel from the Dataset tab.
4. Save an Apify Task and schedule it daily to monitor changes. Enable Only changes to skip unchanged jobs.

Example input:

{
  "careerUrls": ["https://jobs.lever.co/spotify", "https://jobs.ashbyhq.com/notion"],
  "keywords": ["sales", "marketing"],
  "includeDescription": false,
  "maxJobsPerBoard": 5000,
  "changesOnly": false,
  "monitorId": "sales-hiring-watch"
}

Advanced input accepts board identifiers instead of URLs:

{
  "boards": [
    {"ats":"greenhouse","board":"stripe"},
    {"ats":"smartrecruiters","board":"BoschGroup"},
    {"ats":"recruitee","board":"bunq"},
    {"ats":"workable","board":"deeporigin"},
    {"ats":"personio","board":"personio"}
  ]
}

Output

Each job record contains ATS, board, region, jobId, title, company, location, department, employmentType, workplaceType, publishedAt, jobUrl, applyUrl, description, changeType, and checkedAt. Fields not published by a provider are null. Descriptions are optional and may be unavailable from listing endpoints. Salary fields are not inferred.

Example:

{
  "ats": "lever",
  "board": "spotify",
  "region": "global",
  "jobId": "example-id",
  "title": "Marketing Manager",
  "company": "spotify",
  "location": "London",
  "department": "Marketing",
  "employmentType": "Full-time",
  "workplaceType": "hybrid",
  "publishedAt": null,
  "jobUrl": "https://jobs.lever.co/spotify/example-id",
  "applyUrl": "https://jobs.lever.co/spotify/example-id/apply",
  "description": null,
  "changeType": "baseline",
  "checkedAt": "2026-10-05T08:00:00.000Z"
}

This example is illustrative. The Output tab offers Jobs and hiring changes, with overview and full-detail table views, plus a Run summary link. RUN_SUMMARY in the run's key-value store provides counts, errors, truncated boards, and spending-limit status. Output and dataset schemas are included in the Actor source for API and MCP consumers.

Monitoring behavior

changeType	Meaning
baseline	First observation; not a claim that the job was just posted
new	Newly observed since the previous successful check
changed	Published job fields changed
unchanged	Same published fields as before
possibly_closed	Missing from one complete, successful check
closed	Missing from two consecutive complete, successful checks
reopened	Previously closed posting reappeared
board_error	Feed could not be checked; diagnostic record, not a job

Snapshots are isolated by the running user's account and monitor name. When no name is given, the Apify Task ID or board list supplies the identity. Keep one schedule per monitor; concurrent runs can race. A detected snapshot conflict skips the state update and is reported in RUN_SUMMARY. Reuse the same monitor name to retain history. State depends on Apify's retention policy; if it expires, the next run starts a new baseline.

Failures preserve prior snapshots. Truncated scans cannot close unseen jobs. If a spending limit prevents full output, that board's snapshot is not advanced. Switching the description output option does not alter comparison fingerprints. Keywords match titles and departments, case-insensitively; any keyword may match.

Coverage and limitations

• Public feeds only: no accounts, cookies, proxies, or login required.
• Greenhouse and Lever support global and EU career-board URLs.
• SmartRecruiters pagination is followed until the requested cap.
• Company-owned career domains are not automatically resolved to an ATS. Paste the actual provider board URL or supply ats + board.
• Workday is not supported in this release.
• Workable uses its public widget feed; coverage is limited to jobs exposed there. Regional content and upstream access restrictions may differ.
• A confirmed disappearance is a feed observation, not an independent employer confirmation that a vacancy is filled.
• Upstream feeds can change. Unknown response schemas produce errors rather than silently empty boards.
• Limits: 50 boards per run, up to 10,000 jobs per board. A truncated scan is identified in RUN_SUMMARY.

Pricing

Pay per emitted job record, including baseline, unchanged, new, changed, reopened, and closure observations. Filtering and Only changes reduce the number of chargeable records. Board-error diagnostics and RUN_SUMMARY have no Actor event charge.

Apify plan	Per 1,000 job records
Free	$3.00
Bronze	$2.50
Silver	$2.00
Gold, Platinum, Diamond	$1.50

The Store pricing panel is authoritative. Ordinary Apify platform usage charges may also apply according to your plan. Configure Maximum total charge before running. The Actor stops job output at its event budget rather than continuing to generate unbilled records.

Privacy and support

The Actor reads public employer job information. It stores job datasets and monitoring snapshots in Apify storage associated with the running user; it does not send them to an external analytics or AI service. It does not collect applicant data, submit applications, or contact employers.

Use the Actor's Issues tab for support. Include the provider, public board URL, and run ID; do not include account tokens or applicant information. Public Store publication is not proof of customer validation. This is an initial release tested on public boards, not a claim of production adoption.

Local development

Use Node.js 22 or newer. Run npm ci, npm test, then npm start with input in Apify local storage. The Docker image installs pinned dependencies from package-lock.json. No Apify token is embedded in source files.