# Greenhouse & Lever Fresh Jobs Monitor (`technicaldost/greenhouse-lever-fresh-jobs-monitor`) Actor

Monitor public Greenhouse and Lever company boards, normalize real openings, filter by title or location, and emit only new jobs on repeat runs.

- **URL**: https://apify.com/technicaldost/greenhouse-lever-fresh-jobs-monitor.md
- **Developed by:** [Technical Dost Solutions](https://apify.com/technicaldost) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 fresh 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.

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 Fresh Jobs Monitor

Monitor public company career boards on Greenhouse and Lever and receive one normalized dataset row per real opening. It is designed for recruiters, staffing firms, sales teams, job aggregators, and hiring-signal workflows that need repeatable fresh-job data without scraping brittle career-page HTML.

The Actor calls only the official public job-board endpoints documented by Greenhouse and Lever. It does not log in, submit applications, access candidate data, or fetch arbitrary URLs.

### Why use it

- Monitor up to 20 Greenhouse and Lever boards in one bounded run.
- Normalize both providers into one stable output contract.
- Filter by job-title and location keywords before rows are emitted.
- Use `onlyNew` with `stateStoreName` to emit only openings not seen on earlier runs.
- Get honest partial-failure reporting in `RUN_SUMMARY`; failed boards and diagnostics are never dataset rows.
- Pay only for useful dataset rows under the Actor's pay-per-event pricing.

### Quick start

```json
{
  "boards": [
    { "provider": "greenhouse", "slug": "stripe", "companyName": "Stripe" },
    { "provider": "lever", "slug": "palantir", "companyName": "Palantir" }
  ],
  "titleKeywords": ["engineer", "developer"],
  "maxJobsPerBoard": 25,
  "onlyNew": false
}
```

The slug is the company-specific final path segment used by the public ATS board. For Greenhouse, `stripe` maps to the documented `boards-api.greenhouse.io/v1/boards/stripe/jobs` pattern. For Lever, `palantir` maps to `api.lever.co/v0/postings/palantir`.

For a recurring monitor, choose a stable state name and schedule the Actor with `onlyNew: true`:

```json
{
  "boards": [{ "provider": "greenhouse", "slug": "stripe", "companyName": "Stripe" }],
  "onlyNew": true,
  "stateStoreName": "stripe-engineering-watch"
}
```

The first run treats every matching opening as new. Later runs suppress jobs already present in that named state store.

### Output

Each successful row contains:

- `jobId`: stable provider + board + posting identifier
- `provider`, `boardSlug`, and optional user-supplied `company`
- `title`, `location`, `team`, `department`, `commitment`, and `workplaceType` when the source exposes them
- a bounded plain-text description
- public job and application URLs
- source timestamps when available, `capturedAt`, and `isNew`

Example:

```json
{
  "jobId": "lever:palantir:example-id",
  "provider": "lever",
  "boardSlug": "palantir",
  "company": "Palantir",
  "title": "Software Engineer",
  "location": "New York, NY",
  "team": "Engineering",
  "department": "Product Development",
  "commitment": "Full-time",
  "workplaceType": "hybrid",
  "descriptionText": "Build reliable products...",
  "jobUrl": "https://jobs.lever.co/palantir/example-id",
  "applyUrl": "https://jobs.lever.co/palantir/example-id/apply",
  "createdAt": "2026-09-19T08:00:00.000Z",
  "updatedAt": null,
  "sourceUrl": "https://api.lever.co/v0/postings/palantir?mode=json",
  "capturedAt": "2026-09-20T10:00:00.000Z",
  "isNew": true
}
```

Fields not provided by an ATS remain `null`; the Actor does not invent them. `RUN_SUMMARY` is stored separately and records processed boards, failures, duplicates, and only-new suppression.

### Pricing and limits

The planned Store price is **$0.003 per delivered job row**. Invalid inputs, failed boards, duplicates, suppressed old jobs, and the run summary are not billed as results.

- 1–20 boards per run
- 1–500 accepted jobs per board
- up to 10 title filters and 10 location filters
- four total attempts at most for transient `408`, `429`, or `5xx` responses
- 45-second maximum per request and a 10 MB response limit
- state is capped to prevent unbounded storage growth

### Limitations

- Only public, published jobs exposed by the two documented ATS endpoints are included.
- This is a board monitor, not a cross-company search engine; customers supply the company board slugs they want to watch.
- Greenhouse does not expose a reliable created timestamp in its public list response, so `createdAt` is `null`; `updatedAt` is preserved when supplied.
- Lever EU boards require `leverRegion: "eu"`.
- A valid but empty public board succeeds with zero result rows. A missing, private, or malformed board is reported as a failure; the run fails if every requested board fails.

### API example

```bash
curl -X POST "https://api.apify.com/v2/acts/technicaldost~greenhouse-lever-fresh-jobs-monitor/runs?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"boards":[{"provider":"greenhouse","slug":"stripe","companyName":"Stripe"}],"maxJobsPerBoard":10}'
```

Keep Apify tokens in environment variables or a secrets manager; do not commit them or place them in shared logs.

### Local verification

```bash
npm ci
npm test
```

Source behavior is covered with fixtures/mocks for validation, normalization, filtering, only-new state, retries, partial failure, and schema integrity. Release smoke tests use real public Greenhouse and Lever boards with a one-row cap.

# Actor input Schema

## `boards` (type: `array`):

One entry per public board. The slug is the final path part in a Greenhouse or Lever careers URL.

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

Optional case-insensitive filters. A job is kept when its title contains any keyword.

## `locationKeywords` (type: `array`):

Optional case-insensitive filters. A job is kept when its location contains any keyword.

## `maxJobsPerBoard` (type: `integer`):

Stop after this many matching jobs from each board.

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

On repeat runs, suppress job IDs already stored in the selected state store.

## `stateStoreName` (type: `string`):

Use a stable name to isolate repeat monitors. Letters, numbers, underscore and hyphen only.

## Actor input object example

```json
{
  "boards": [
    {
      "provider": "greenhouse",
      "slug": "stripe"
    },
    {
      "provider": "lever",
      "slug": "palantir"
    }
  ],
  "maxJobsPerBoard": 50,
  "onlyNew": false,
  "stateStoreName": ""
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `jobsCsv` (type: `string`):

No description

## `runSummary` (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 = {
    "boards": [
        {
            "provider": "greenhouse",
            "slug": "stripe"
        },
        {
            "provider": "lever",
            "slug": "palantir"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("technicaldost/greenhouse-lever-fresh-jobs-monitor").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 = { "boards": [
        {
            "provider": "greenhouse",
            "slug": "stripe",
        },
        {
            "provider": "lever",
            "slug": "palantir",
        },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("technicaldost/greenhouse-lever-fresh-jobs-monitor").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 '{
  "boards": [
    {
      "provider": "greenhouse",
      "slug": "stripe"
    },
    {
      "provider": "lever",
      "slug": "palantir"
    }
  ]
}' |
apify call technicaldost/greenhouse-lever-fresh-jobs-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,technicaldost/greenhouse-lever-fresh-jobs-monitor"
        }
    }
}
```

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/37dGSVBT5GZdR8X8X/builds/QgmiEEJKScmgUWl4C/openapi.json