ATS Job Feed — Greenhouse, Lever & Ashby Changes

Enter a public Greenhouse, Lever or Ashby board slug together with its provider.
Download job titles, locations, departments, descriptions and links in one consistent dataset.

Large boards and validation

All provider/board input objects are validated before any requests or charges. Greenhouse uses content=false to keep large boards bounded; its result descriptions are therefore empty. Lever and Ashby retain descriptions supplied by their public APIs. Results and state fingerprints are saved in batches of up to 100, with state advanced only for delivered rows. Maximum rows and source counts are limits, not guaranteed throughput under the shared request/byte/time budgets.

Real output example

Captured on 2026-09-14 from run tcahlLkTMgECXLgpY using the input below. Selected fields are shown; long values are shortened with an ellipsis. Live source data can change.

provider	title	location
greenhouse	Commercial Counsel	Eastern Timezone
greenhouse	Director, People Systems and Operations	Anywhere in the United States
greenhouse	Engineering Manager, Cloud Platform	Ontario

The first-run example intentionally stops at 3 results. LIMIT_REACHED is expected and does not mean the complete store, board or feed was collected.

Quick start

1. Leave the prefilled example in place and click Start for a small first run. Replace it with your own source when ready.
2. Set Maximum delivered results and Apify's Maximum cost per run.
3. Run the Actor. Export the dataset as JSON, CSV or Excel. Open Run report for errors, skipped items and limits.

{
  "boards": [
    {
      "provider": "greenhouse",
      "board": "greenhouse"
    }
  ],
  "maxResults": 3
}

What it supports

Supply up to 20 exact board slugs with provider greenhouse, lever or ashby. Lever also accepts region="eu". Public posting APIs only: no applications, resumes or private vacancies. No invented salary or posted date; missing fields are null. Lever and Greenhouse do not consistently expose a published date. Optional onlyChanges compares content hashes in your named state store and emits NEW or UPDATED, not closed/removed jobs. Query the same boards without overlapping runs. Up to 5,000 Lever postings per source; a report warning marks that cap. Optional keywords (matched in title, department or description; Greenhouse descriptions are empty) and locations (matched in location or workplace type) are case-insensitive text filters applied before any result is emitted or billed; RUN_REPORT.sources[].filteredOut counts the skipped jobs.

Price

$0.0015 per job posting ($1.5 per 1,000), plus $0.001 per run start at the supported 512 MB–1 GB memory sizes. The custom result event is charged only for a delivered dataset row. There is no separate automatic dataset-row fee. A run that returns zero rows still incurs the start fee. Your account's displayed pricing and platform terms apply. Actor authors pay their own platform resource costs during development and testing.

Set the maximum cost in Apify to cap spending. maxResults also limits output. A limit may truncate a catalog or comparison; inspect RUN_REPORT rather than assuming completeness.

Output and reliability

Main fields: provider, board, title, location, department, url. Each row includes observedAt. Nested values remain JSON; choose JSON export to preserve all detail.

RUN_REPORT contains result count, HTTP request/download totals, source errors, skipped unchanged items and final status. PARTIAL means at least one source failed while other rows were delivered. FAILED means no successful result and at least one error. Successful empty feeds or no-change comparisons can legitimately return zero rows. A 240-second processing deadline and Apify's run timeout bound execution. Downloads are limited to 40 MB per run, with smaller per-response caps; robots checks count as requests. No proxy or external AI API subscription is required.

Only public pages and documented public APIs are supported. Access restrictions are reported. The crawler does not send your Apify token to target websites or connect to private network addresses. Use sources you are entitled to access. Static HTML tools do not execute website JavaScript.

Repeated runs

For Actors with stateStoreName, use a distinct name for each collection and keep the same name for later runs. Apify creates that store in your account; storage retention and access follow your account settings. Do not start overlapping runs that share a store. onlyChanges emits new/updated items and retains at most 10,000 recent fingerprints. It does not infer removed pages/jobs. Other Actors are stateless: supply fresh inputs, or feed their datasets into the Dataset Change Detector.

Apify tasks, schedules and integrations can reuse this input. No recurring schedule or customer notification is created automatically.

عربي

أداة جاهزة للتشغيل من واجهة Apify أو API. أدخل الروابط أو البيانات، وحدد عدد النتائج والحد الأعلى للتكلفة. النتائج بصيغ JSON وCSV وExcel، والتفاصيل والأخطاء في RUN_REPORT. البيانات العامة فقط؛ الحقول غير المتوفرة تبقى فارغة. راجع حدود الأداة أعلاه قبل اعتماد النتائج.