# Greenhouse, Lever & Ashby Jobs Scraper & API: Postings to JSON (`lepidata/new-jobs-feed`) Actor

Greenhouse, Lever & Ashby jobs from company career sites as clean JSON. Filter by company, title or location. $0.90 per 1,000 jobs on paid plans.

- **URL**: https://apify.com/lepidata/new-jobs-feed.md
- **Developed by:** [Lepi Data](https://apify.com/lepidata) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.90 / 1,000 job results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Greenhouse, Lever & Ashby Jobs Scraper & API: Postings to JSON

### What it does

We keep a directory of public job boards from 9,500+ companies with open jobs on Greenhouse, Lever and Ashby. The feed is updated daily. You search it: for example, every "data engineer" job that appeared in the last 24 hours in Germany. You get matching jobs in one clean format, with a link to apply on the employer's own site.

### Common uses

- **Job alerts by title and location**: a daily feed of new "data engineer" or "product manager" jobs, straight from company career sites (no LinkedIn or Indeed).
- **Job board API for your own site or newsletter**: one ATS jobs feed covering Greenhouse, Lever and Ashby, as JSON, CSV or Excel.
- **Hiring signals for sales**: see which companies just opened roles in your niche.
- **Remote jobs feed**: turn on *Remote only* to get remote jobs posted in the last 24 hours.

### Example inputs

Paste any of these into the JSON input tab:

**Software engineers, last 72 hours**

```json
{"titleKeywords": ["software engineer"], "postedWithinHours": 72, "includeDescriptions": false, "maxJobs": 100}
```

**Product managers, last 7 days**

```json
{"titleKeywords": ["product manager"], "postedWithinHours": 168, "includeDescriptions": false, "maxJobs": 100}
```

**Ashby-only sales roles (hiring signal)**

```json
{"titleKeywords": ["account executive", "sales"], "platforms": ["ashby"], "postedWithinHours": 168, "maxJobs": 200}
```

### Search filters

- Title keywords (matches any), plus title words to exclude
- Location contains
- Remote only
- New in the last N hours (based on when our crawl first saw the job; for a company's first check, the employer's posting date)
- Platform (Greenhouse, Lever or Ashby)
- Also return changed jobs: older jobs whose title, location or description text changed in your time window (a new date alone doesn't count)
- Companies to include or exclude

### Output (one item per job)

Same core fields as our single-platform Actors (source, company, jobId, title, department, location, url to the employer's original posting, firstPublished, description), plus firstSeenAt and lastSeenAt from our crawl. Descriptions are fetched live from the employer's board when you run it; a job that has come down since our last check is skipped and not billed.

### Freshness and coverage, honestly

- Directory size: 9,500+ companies with open jobs, counted Oct 11, 2026.
- The feed is updated once a day. A new posting shows up after our next update, so it can take up to about a day to appear.
- If an update is ever missed and the data is more than 30 hours old, your run still returns results, plus one free `feed-stale` row saying how old the data is. You're never charged for that row.
- Covers Greenhouse, Lever and Ashby only. It does not cover Workday (use our separate Workday Actor for that), job boards like LinkedIn or Indeed, or other hiring platforms.
- Closed postings leave the open feed within about a day.
- **Closed-job alerts included free:** turn on closed jobs and get a free row for each matching job that closed within your time window, up to the last 7 days (job ID, company, title and the time we saw it close).
- Want a company added? Tell us in an issue and we'll add it if it's on a supported platform.

### Why use this one

- **Fresh descriptions.** We fetch each job's description from the employer's board when you run the search, so you get the current text, and a job that came down since our last check is skipped and not billed.
- **Closed-job alerts are free.**
- **Updated and checked every day.** If an update is missed, your run tells you with a free `feed-stale` row instead of silently serving old data.
- **Status rows are free.** `feed-stale`, `charge-limit-reached` and closed-job rows are never charged.
- **Missing descriptions are free, up to 5% per run.** If you ask for descriptions and we can't fetch one from the employer's board, that job is still returned, marked `descriptionMissing`, and not charged. Free rows are capped at 5% of a run's jobs; any beyond that are billed as normal jobs, marked `descriptionMissingBilled`, and the run log says so.
- **Exact price, no surprises.** You pay only for the jobs delivered, at the price shown below.

### Pricing

$0.90 per 1,000 jobs on every paid Apify plan, plus Apify's standard run-start fee. Closed-job rows are free.

On Apify's Free plan the price is higher, $40 per 1,000 jobs, and each run returns up to 25 jobs so you can try the feed (about $1 of a free account's monthly credit). The run ends with one free row explaining the limit. Paid Apify plans get full results at the prices above.

### Data use

Job data only, no personal profiles. Every job links back to the employer's original posting. If an employer or platform asks us to stop including their jobs, we remove them.

### Credits

Includes data from LastRound AI's ATS Company Directory ([CC BY 4.0](https://datahub.io/lastroundai-hiring-data/lastroundai-hiring-data/ats-directory)), from LastRound AI's [salary transparency study](https://lastroundai.com/blog/salary-transparency-study-2026), re-verified and filtered by us. Also uses the [Job board directory](https://kalebconfer-sys.github.io/job-board-directory/) (CC0).

### Not affiliated

This Actor is an independent, unofficial tool. It is not made, endorsed, or supported by Greenhouse Software, Inc., Lever, Ashby, or any employer whose jobs it lists. Platform names describe the sources only. Phone numbers and personal email addresses are removed. Company role addresses, like accommodations or recruiting inboxes, are kept so applicants can reach them.

# Actor input Schema

## `titleKeywords` (type: `array`):

Return jobs whose title contains any of these (case-insensitive, matched at the start of a word: "engineer" also finds "Engineering"). Empty = any title.

## `excludeTitleKeywords` (type: `array`):

Skip jobs whose title contains any of these.

## `locations` (type: `array`):

Return jobs whose location text contains any of these, e.g. Germany, Berlin, Remote. Empty = anywhere.

## `remoteOnly` (type: `boolean`):

Only jobs whose location says remote. Check each posting for country or time-zone limits.

## `postedWithinHours` (type: `integer`):

Jobs our crawl first saw in this many hours (not the employer's posting date). Max 168 (7 days).

## `includeChanged` (type: `boolean`):

Also return older jobs whose title, location or description text changed in that window. A new date on the posting alone doesn't count.

## `platforms` (type: `array`):

Limit to these hiring platforms. Empty = all.

## `companies` (type: `array`):

Board URLs, board names (e.g. stripe) or company names. Empty = all companies in the feed.

## `excludeCompanies` (type: `array`):

Board URLs, board names or company names to skip.

## `includeDescriptions` (type: `boolean`):

Fetch descriptions live from each employer's public board (one request per company per run). Jobs taken down since our last check are skipped and not charged. If a board can't be fetched just then, its jobs are still returned with no description, descriptionStatus 'unavailable' and descriptionMissing true. Those rows are free up to 5% of the jobs delivered in the run; past that they are charged and marked descriptionMissingBilled.

## `includeClosed` (type: `boolean`):

Add a free row for each matching job that closed in the time window: job ID, company, title and close time.

## `maxJobs` (type: `integer`):

Stop after this many job rows. Your maximum charge per run is also honoured: the run stops before going over it.

## `emailPolicy` (type: `string`):

Phone numbers and personal email addresses are always removed.

## Actor input object example

```json
{
  "titleKeywords": [
    "software engineer"
  ],
  "remoteOnly": false,
  "postedWithinHours": 72,
  "includeChanged": false,
  "includeDescriptions": false,
  "includeClosed": false,
  "maxJobs": 100,
  "emailPolicy": "keep-role"
}
```

# Actor output Schema

## `jobs` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "titleKeywords": [
        "software engineer"
    ],
    "postedWithinHours": 72,
    "maxJobs": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("lepidata/new-jobs-feed").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "titleKeywords": ["software engineer"],
    "postedWithinHours": 72,
    "maxJobs": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("lepidata/new-jobs-feed").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "titleKeywords": [
    "software engineer"
  ],
  "postedWithinHours": 72,
  "maxJobs": 100
}' |
apify call lepidata/new-jobs-feed --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,lepidata/new-jobs-feed"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/avHclADG0txPVRu5Z/builds/qfG41NzEri9wWbwkK/openapi.json