Company Job Postings (Greenhouse, Lever, Ashby)
company_job_postingsCollect open job postings from Greenhouse, Lever, and Ashby career boards in one call, returning company, title, location, department, posting date, salary, and apply URL as structured rows.
Instructions
Collect live job postings straight from company career boards in one call: one row per open job with company, ATS, job id, title, location, department, employment type, workplace type, posting date, apply URL, salary text when the board publishes it, and the description as plain text (optional). Give it board tokens or career-page URLs for Greenhouse ('stripe'), Lever ('leverdemo') or Ashby ('ramp'). A call must name at least one board.
Behavioral Transparency:
Execution: Network call executed synchronously in the cloud via Apify Actor 'captainhandsome/job-postings-scraper'.
Side Effects: Reads each platform's public job-board JSON endpoint (the same data the company's own careers page loads) and creates a billed Actor run and dataset on your Apify account. No login, no API key, no cookies, no browser.
Authentication: Requires APIFY_TOKEN environment variable.
Latency & Limits: Typically 2-20 seconds. $0.003 per job row plus $0.005 per run. This tool sends at most 3 boards per platform and at most 10 jobs per board, so one call bills at most 90 rows; raise max_jobs_per_company only if you want larger boards. (The Actor itself accepts more boards and jobs when called directly on Apify.)
Usage Guidelines:
When to use: Use for hiring-signal lead lists (which accounts are opening which roles), job-market research across a handful of companies, recruiting and competitor intel, or filling a job board or newsletter with fresh roles from companies you choose.
When NOT to use: Do not use for closed or archived postings (boards expose currently open jobs only), for LinkedIn, Indeed or ZipRecruiter aggregator data, or for Workable boards (its public endpoint rate-limits datacenter IPs and is deliberately not supported).
Named alternatives: the other tools in this package cover Shopify catalogs, app stores, podcasts and newsletters, not job boards.
Honest limits: only Greenhouse, Lever and Ashby are supported; a private or removed board returns nothing for that company and the run continues with the rest; boards that publish no posting date or salary leave those fields null rather than inventing them; descriptions are trimmed to 4,000 characters. Board lists are sent explicitly on every call, so an omitted platform is skipped, never replaced by a hidden default search.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "company_job_postings"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ashby | No | Up to 3 Ashby organisation names or URLs, e.g. 'ramp' or 'https://jobs.ashbyhq.com/ramp'. Leave out to skip Ashby. | |
| lever | No | Up to 3 Lever board tokens or URLs, e.g. 'leverdemo' or 'https://jobs.lever.co/leverdemo'. Leave out to skip Lever. | |
| query | No | Optional keyword filter applied to job title and description, e.g. 'engineer'. Leave empty for all jobs. | |
| greenhouse | No | Up to 3 Greenhouse board tokens or URLs, e.g. 'stripe' or 'https://boards.greenhouse.io/stripe'. Leave out to skip Greenhouse. | |
| posted_within_days | No | Keep only jobs posted in the last N days. 0 means no date filter; boards that expose no date are kept. | |
| include_description | No | When true, each row carries the posting description as plain text trimmed to 4,000 characters. Set false for a smaller, faster dataset. | |
| max_jobs_per_company | No | Upper limit of postings returned per board (hard maximum 10). Each row is a billed result. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| run | No | ||
| error | No | ||
| status | Yes | ||
| results | Yes |