Company Career-Page Jobs Export avatar

Company Career-Page Jobs Export

Pricing

$2.00 / 1,000 completed results

Go to Apify Store
Company Career-Page Jobs Export

Company Career-Page Jobs Export

Export published jobs from supplied Greenhouse, Lever, and Ashby boards into one schema, with descriptions, source compensation, stable IDs, and explicit board coverage.

Pricing

$2.00 / 1,000 completed results

Rating

0.0

(0)

Developer

JJ Toolworks

JJ Toolworks

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Categories

Share

Import published jobs from employer boards on Greenhouse, Lever, and Ashby. Supply the boards you want to monitor and receive a common schema, descriptions, application links, and a coverage row for every input.

Start a run

{
"boards": [
{"provider": "greenhouse", "board": "greenhouse", "label": "Greenhouse public board"}
],
"maxJobsPerBoard": 20,
"maxJobsTotal": 20,
"maxScanPerBoard": 500,
"titleKeywords": []
}

board accepts a board token or a supported HTTPS board URL. Lever supports US and EU boards (region: "eu", or a jobs.eu.lever.co board URL). Optional clientId and label preserve your own mapping. Repeated board inputs are fetched once. A duplicate board with a different label does not create another copy of every job; use the board identity to join your input mappings.

Output and useful workflows

Filter recordType=job for the paid job results. Each includes recordId, source/provider/board identity, your client label, title, location, employment/workplace fields when supplied, descriptionText, descriptionHtml, jobUrl, applyUrl, compensation when included in the source response, and fetch/source timestamps. Source descriptions are untrusted HTML; sanitize them before rendering in a website.

Filter recordType=board_status to inspect completeness and limits. The SUMMARY key-value-store record includes all board statuses. Dataset CSV/JSON exports are available through Apify. Use saved tasks and Apify schedules for employer watchlists, niche job boards, or recruiting research. A company label is your input, not verified legal-entity data.

complete means the supported source listing was retrieved and the selected scan/output limits did not omit matching valid jobs. It never means a complete global company inventory. Partial/failed/truncated runs must not be used to infer a job closed. Unknown remote or compensation fields remain unknown. Greenhouse compensation generally needs a separate per-job API request and is not fetched in this base version. Greenhouse prospect posts and Ashby jobs without isListed=true are excluded.

Bounds and charging

One event per distinct published job emitted in a run. Duplicate jobs, duplicate boards, empty results, failed-board records, and summary/status rows are unbilled. Filtering can still require retrieving many source records; use maxScanPerBoard to bound work. Selected limits can yield a valid truncated result. A run does not retry failed pages automatically.

Hard limits: 50 boards, 1,000 jobs/board, 5,000 jobs/run, 5,000 scanned source records/board, and 8 MiB per source response. Lever fetches 100-record pages with a bounded look-ahead; Greenhouse and Ashby return bounded complete list responses. Malformed/oversized responses are reported instead of silently becoming empty boards.

This Actor reads public job-board APIs. It does not collect applicants or submit applications. Supported-source documentation: Greenhouse, Lever, and Ashby. Published source data, API availability, and customer redistribution rights can vary; retain original links and use the data within your permitted workflow.

Price and run controls

The launch price is $2 per 1,000 completed units ($0.002 per event), as defined above. Check the current Pricing tab before running. Status and duplicate rows do not add this custom event. Set a maximum charge appropriate for your batch; a run stops when its event budget is exhausted. RUN-SUMMARY records actual accepted events and execution totals.

Automatic replay of an interrupted run is disabled to prevent duplicate charges. Keep the available output, then start a new run for a new execution. A later run is a new billable execution. Completed dataset rows and individually saved files remain available when a budget stops a run. Combined exports, manifests, and snapshots assembled at the end may be absent after a budget stop or interruption; use a sufficient run budget when you need those aggregate files. The initial release uses documented input limits and public source access; external source changes can require maintenance.