# Greenhouse, Lever & Ashby Jobs Scraper - New Job Postings Feed (`northbound-labs/ats-new-jobs-feed`) Actor

Scrape new job postings from Greenhouse, Lever and Ashby job boards in one normalized feed. Keyword and location filters, dedupe across runs.

- **URL**: https://apify.com/northbound-labs/ats-new-jobs-feed.md
- **Developed by:** [NorthBound Labs](https://apify.com/northbound-labs) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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 - New Job Postings Feed

Scrape **new job postings from company career pages on Greenhouse, Lever and Ashby** in one normalized feed. List the companies you care about, filter by keyword and location, and get only new jobs on every scheduled run.

- **Official source:** the public job-board APIs of Greenhouse, Lever and Ashby.
- **No login, no browser, no personal data.**
- **Monitoring built in:** turn on *Only new since last run* and schedule it for a daily alert feed.
- **Export** to JSON, CSV, Excel, HTML or straight into Google Sheets, Slack, Zapier, Make, n8n or your own code via the Apify API.

### What can you use it for?

- **Recruiters and job boards:** aggregate fresh postings from the companies you track.
- **Sales teams:** use new hiring as a buying signal (for example, a company hiring its first data engineer).
- **Job seekers:** watch target companies and get new roles first.

### How to use it

1. Click **Try for free** (or **Start**). The input is pre-filled, so the first run works with one click and finishes in seconds.
2. Adjust the filters in the **Input** tab (see the table below).
3. Click **Start** and open the **Output** tab. The *Overview* view shows the key columns; *All fields* shows everything.
4. Download the results (JSON, CSV, Excel...) or connect them to your tools (see *Scheduling and integrations*).

### Input

| Field | Name | What it does |
|---|---|---|
| `companies` | Companies (ATS:board token) | One per line as ats:token, e.g. greenhouse:stripe, lever:palantir, ashby:ramp. A bare token is tried on all three ATSs. |
| `keywords` | Keywords | Match any keyword (case-insensitive). Empty = all. |
| `location` | Location contains | Keep jobs whose location contains this text (case-insensitive). |
| `daysBack` | Days back | How many days back to look. Default 30. On scheduled runs with 'Only new since last run' on, a small window (1-3 days) is enough. |
| `maxItems` | Max results | Stop after this many results. You pay per result ($2 per 1,000), so this caps your cost: 100 results = $0.20. |
| `onlyNew` | Only new since last run | Skip records already returned by earlier runs of this Actor in your Apify account, so each run outputs only new ones. Turn on for scheduled daily alerts; leave off for a one-off full export. |

Example input:

```json
{
  "companies": [
    "greenhouse:stripe",
    "lever:palantir",
    "ashby:ramp"
  ],
  "keywords": [
    "engineer"
  ],
  "daysBack": 30,
  "maxItems": 20,
  "onlyNew": true
}
```

### Output

Each result is one record with these fields:

| Field | Description |
|---|---|
| `ats` | Applicant tracking system: greenhouse, lever or ashby. |
| `company` | Company name. |
| `boardToken` | The company's job-board token on the ATS. |
| `jobId` | Job ID on the ATS. |
| `title` | Job title. |
| `location` | Job location as posted. |
| `department` | Department or team, when given. |
| `employmentType` | e.g. FullTime, when given. |
| `remote` | Remote flag, when the ATS provides one. |
| `postedAt` | When the job was posted. |
| `updatedAt` | When the job was last updated. |
| `jobUrl` | Link to the job posting. |

Sample result (from a real run, long values shortened):

```json
{
  "ats": "greenhouse",
  "company": "Stripe",
  "boardToken": "stripe",
  "jobId": "8138044",
  "title": "Account Executive, AI Sales",
  "location": "San Francisco, CA",
  "department": null,
  "employmentType": null,
  "remote": null,
  "postedAt": "2026-09-18T13:27:51-04:00",
  "updatedAt": "2026-10-07T19:02:27-04:00",
  "jobUrl": "https://stripe.com/jobs/search?gh_jid=8138044"
}
```

### Scheduling and integrations

- **Daily alerts:** in Apify Console, open **Schedules**, create a schedule (for example every day at 08:00) for this Actor with `onlyNew: true`. Each run then returns only records that are new since the previous run.
- **Webhooks:** add a webhook on *Run succeeded* to call your own endpoint, Slack or a workflow tool when new data is ready.
- **Zapier, Make, n8n, Google Sheets, Slack, email:** use Apify's ready-made integrations on the Actor's **Integrations** tab to push each run's dataset wherever you work.
- **API:** run it and get results in one call:

```bash
curl -X POST "https://api.apify.com/v2/acts/northbound-labs~ats-new-jobs-feed/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"companies": ["greenhouse:stripe", "lever:palantir", "ashby:ramp"], "keywords": ["engineer"], "daysBack": 30, "maxItems": 20, "onlyNew": true}'
```

Or with the Apify Python client: `ApifyClient(token).actor("northbound-labs/ats-new-jobs-feed").call(run_input={...})`.

### Pricing

This Actor uses **pay-per-event** pricing, so you pay only for what you get:

- **$2.00 per 1,000 results** ($0.002 per result).
- An Actor start event of $0.00005 per run at the default 512 MB memory.

| You get | Cost |
|---|---|
| 20 results (the pre-filled test run) | about $0.04 |
| 100 results | about $0.20 |
| 1,000 results | about $2.00 |
| A daily schedule returning ~50 new results a day for 30 days | about $3.00 a month |

Set **Max results** to cap the cost of any run. Apify's free plan includes monthly credit you can use to try it.

### FAQ

**How do I find a company's board token?**
It's in the company's careers URL: boards.greenhouse.io/**stripe**, jobs.lever.co/**palantir**, jobs.ashbyhq.com/**ramp**. Enter it as `greenhouse:stripe`. A bare token is tried on all three ATSs.

**Does it include applicant or recruiter data?**
No. Only public job-posting fields.

**Do I need an account on the source site?**
No. The Actor reads public, logged-out data from Greenhouse, Lever and Ashby through its official interface.

**Does it return personal data?**
No. Output is limited to organisation-level and record-level fields.

**How fresh is the data?**
As fresh as the source: every run queries it live.

**Is it legal to use this data?**
The data comes from an official public source. You are responsible for using it in line with the source's terms and the laws that apply to you.

**Something broken, or a field you need?**
Open an issue on the **Issues** tab. We read every issue and reply as fast as we can.

# Actor input Schema

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

One per line as ats:token, e.g. greenhouse:stripe, lever:palantir, ashby:ramp. A bare token is tried on all three ATSs.

## `keywords` (type: `array`):

Match any keyword (case-insensitive). Empty = all.

## `location` (type: `string`):

Keep jobs whose location contains this text (case-insensitive).

## `daysBack` (type: `integer`):

How many days back to look. Default 30. On scheduled runs with 'Only new since last run' on, a small window (1-3 days) is enough.

## `maxItems` (type: `integer`):

Stop after this many results. You pay per result ($2 per 1,000), so this caps your cost: 100 results = $0.20.

## `onlyNew` (type: `boolean`):

Skip records already returned by earlier runs of this Actor in your Apify account, so each run outputs only new ones. Turn on for scheduled daily alerts; leave off for a one-off full export.

## Actor input object example

```json
{
  "companies": [
    "greenhouse:stripe",
    "lever:palantir",
    "ashby:ramp"
  ],
  "keywords": [
    "engineer"
  ],
  "daysBack": 30,
  "maxItems": 20,
  "onlyNew": false
}
```

# Actor output Schema

## `results` (type: `string`):

All records returned by the run (default dataset, overview view).

# 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 = {
    "companies": [
        "greenhouse:stripe",
        "lever:palantir",
        "ashby:ramp"
    ],
    "keywords": [
        "engineer"
    ],
    "daysBack": 30,
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("northbound-labs/ats-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 = {
    "companies": [
        "greenhouse:stripe",
        "lever:palantir",
        "ashby:ramp",
    ],
    "keywords": ["engineer"],
    "daysBack": 30,
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("northbound-labs/ats-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 '{
  "companies": [
    "greenhouse:stripe",
    "lever:palantir",
    "ashby:ramp"
  ],
  "keywords": [
    "engineer"
  ],
  "daysBack": 30,
  "maxItems": 20
}' |
apify call northbound-labs/ats-new-jobs-feed --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,northbound-labs/ats-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/s0emEydQ1BDSx1ssg/builds/dQrgqLRcAQ4fGfPUe/openapi.json