# Career-Site Jobs Monitor (Greenhouse, Lever, Ashby) (`brightish_ascent/career-site-jobs-monitor`) Actor

Unofficial; not affiliated with Greenhouse, Lever or Ashby. Monitor company career-site jobs via their official public job-board APIs. Filter by title, location, department, remote. Only-new, changed and removed postings.

- **URL**: https://apify.com/brightish_ascent/career-site-jobs-monitor.md
- **Developed by:** [Michael Rice](https://apify.com/brightish_ascent) (community)
- **Categories:** Business, Developer tools, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 job rows

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

## Career-Site Jobs Monitor (Greenhouse, Lever, Ashby)

Unofficial tool. Not affiliated with or endorsed by Greenhouse, Lever, Ashby or any company listed.

Track open jobs straight from company career sites. The Actor reads each company's public job board through the **official public job-board APIs** of Greenhouse, Lever and Ashby. No login, no proxies, no scraping of LinkedIn or Indeed. In monitor mode it tells you which jobs are **new**, which **changed** (with the previous values), and which were **removed**. A removed posting usually means the job was filled or closed.

### What you get

- **One row per job.** Each row has the company, title, department, team, location (plus all locations), workplace type, employment type, salary range (when the company publishes it), published date, job URL and apply URL.
- **Optional plain-text job description** (`includeDescription`).
- **Monitor mode** (`onlyNewSinceLastRun`):
  - The first run is a baseline: every matching job comes back as `new`.
  - Later runs return only:
    - `new`: jobs not seen before.
    - `changed`: the title, location, department, workplace type, employment type or salary changed. These rows carry a `previous` object with the old values.
    - `removed`: a remembered job is no longer listed, or no longer matches your filters. We only report this for boards read completely in that run, so a failed request never creates false "removed" rows.
- **Filters:** title keywords, excluded keywords, location, department or team, workplace type (remote, hybrid or on-site).
- **Exact `truncated` flag.** It is `true` only when more rows existed than were delivered. In monitor mode, rows that didn't fit are delivered on the next run.

### Input example

```json
{
  "companies": ["greenhouse:stripe", "lever:palantir", "ashby:ramp"],
  "keywords": ["engineer"],
  "locations": ["New York", "Remote"],
  "onlyNewSinceLastRun": true,
  "maxItems": 200
}
```

- **Companies:** use `ats:board` (for example `greenhouse:stripe`), a job-board URL (`https://jobs.lever.co/palantir`), or just the board name. With a bare name we try Greenhouse, then Lever, then Ashby.
- **Finding the board name:** it's the last part of the company's job-board URL.
- **Limits:** up to 50 companies per run. Split bigger lists into several tasks or schedules.

### Output example (full row)

```json
{
  "jobKey": "ashby:ramp:c0a71032-1efb-40dc-b1e8-aa0f30cd5961",
  "ats": "ashby", "companyToken": "ramp", "companyName": "ramp",
  "title": "Senior Backend Engineer | Accounting", "department": "Engineering", "team": "Backend",
  "location": "New York, NY (HQ)", "allLocations": ["New York, NY (HQ)", "San Francisco, CA"],
  "workplaceType": "hybrid", "workplaceTypeSource": "ats", "employmentType": "FullTime",
  "salaryMin": 172000, "salaryMax": 280000, "salaryCurrency": "USD", "salaryInterval": "1 YEAR",
  "salaryText": "$172K – $280K • Offers Equity",
  "publishedAt": "2026-10-21T18:22:42.345Z",
  "url": "https://jobs.ashbyhq.com/ramp/c0a71032-1efb-40dc-b1e8-aa0f30cd5961",
  "updateType": "new", "previous": null, "changeHash": "bc3b46ea722c2dc0", "source": "Ashby Posting API"
}
```

The **run summary** is saved to the `OUTPUT` record in the key-value store. It includes the row count, charged count, which boards were found, not found or failed, new/changed/removed counts, and request stats.

### Good to know

- **What each ATS publishes:**
  - **Salary:** Lever and Ashby include it when the company publishes it. The Greenhouse list API doesn't include pay, so those salary fields are `null`.
  - **Workplace type:** Lever and Ashby publish it. For Greenhouse it is set to `remote` only when the location text says "Remote" (`workplaceTypeSource: "inferred"`); otherwise it's `null`.
  - **Company name:** Lever and Ashby don't send a display name, so `companyName` is the board name.
- **Workday, iCIMS, SmartRecruiters** and other systems are not supported in this version.
- **Monitor state** is kept per filter set in a named key-value store (`career-site-jobs-monitor-state`) in your own Apify account. Changing filters starts a new baseline.
- **Request pacing:** at least 250 ms between API requests, with retries on 429/5xx errors.

### Pricing

Pay per event: a small charge per Actor start plus one charge per dataset row (`job`). A `removed` row is also a dataset row, so it is charged as one `job`. The run's maximum total charge is respected, and rows beyond it are not pushed.

### FAQ

**Is this legal to use?** It uses the documented public job-board APIs that Greenhouse, Lever and Ashby provide so job listings can be shown elsewhere. Job content belongs to the company that posted it. Check that your use fits each company's and provider's terms.

**Why is a company not found?** Check that it actually uses Greenhouse, Lever or Ashby and that the board name is right. The not-found boards are listed in `companiesNotFound`.

Support: digitalpromohub.support@gmail.com

# Actor input Schema

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

Company job boards to read (max 50). Use "greenhouse:stripe", "lever:palantir", "ashby:ramp", a board URL (boards.greenhouse.io/..., jobs.lever.co/..., jobs.ashbyhq.com/...), or just the board name (we try Greenhouse, then Lever, then Ashby).

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

Keep jobs whose title contains ANY of these (case-insensitive). Empty = all jobs.

## `excludeKeywords` (type: `array`):

Drop jobs whose title contains any of these (e.g. "intern", "senior").

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

Keep jobs whose location text contains ANY of these (e.g. "New York", "Remote", "Canada").

## `departments` (type: `array`):

Keep jobs whose department or team contains ANY of these (e.g. "Engineering").

## `workplaceTypes` (type: `array`):

Keep only these workplace types. Lever and Ashby publish this field; for Greenhouse it is inferred as remote only when the location says "Remote" (others are unknown and filtered out).

## `includeDescription` (type: `boolean`):

Add the plain-text job description (max 20,000 characters) to each row. Larger output; not part of change detection.

## `onlyNewSinceLastRun` (type: `boolean`):

Remember jobs per filter set in a named key-value store in your account. Later runs return only new jobs, changed jobs (title, location, department, workplace type, employment type or salary) with previous values, and removed jobs. The first run is a baseline that returns all matching jobs as new.

## `reportRemoved` (type: `boolean`):

Monitor mode only: add a row with updateType "removed" when a remembered job is no longer listed (filled or closed) or no longer matches your filters. Only for boards read completely in that run.

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

Maximum dataset rows per run (each row is one charged event). In monitor mode, rows over the limit are delivered on the next run.

## `outputFormat` (type: `string`):

full = all fields; compact = jobKey, updateType, companyName, title, location, workplaceType, salaryText, publishedAt, url, previous, changeHash.

## Actor input object example

```json
{
  "companies": [
    "greenhouse:stripe",
    "lever:palantir",
    "ashby:ramp"
  ],
  "includeDescription": false,
  "onlyNewSinceLastRun": false,
  "reportRemoved": true,
  "maxItems": 200,
  "outputFormat": "full"
}
```

# Actor output Schema

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

Default dataset. full rows: jobKey (ats:board:jobId), ats, companyToken, companyName, jobId, title, department, team, location, allLocations, workplaceType (remote | hybrid | onsite | null), workplaceTypeSource (ats | inferred | null), employmentType, salaryMin, salaryMax, salaryCurrency, salaryInterval, salaryText, publishedAt, updatedAt (Greenhouse only), url, applyUrl, description (only with includeDescription), updateType (monitor mode: new | changed | removed; otherwise null), removedDetectedAt, previous (changed and removed rows), changeHash, source. compact rows: jobKey, updateType, companyName, title, location, workplaceType, salaryText, publishedAt, url, previous, changeHash.

## `runSummary` (type: `string`):

Fields: ok, count, chargeEvent, chargedCount, chargeLimitReached (only when hit), outputFormat, matchingJobs, companiesResolved (company, ats, board, listedJobs, matchingJobs, complete), companiesNotFound, companiesFailed, truncated (true only when more rows exist than were delivered), truncationNote, message, warnings, onlyNewSinceLastRun, watermarkStore, watermarkKey, baselineRun, newCount, changedCount, removedCount (counted from pushed rows), skippedUnchanged, apiRequests (total, retries, throttled, capped, minIntervalMs, perRunCap, userAgent), disclaimer. On failure: ok false, error.

# 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"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("brightish_ascent/career-site-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 = { "companies": [
        "greenhouse:stripe",
        "lever:palantir",
        "ashby:ramp",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("brightish_ascent/career-site-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 '{
  "companies": [
    "greenhouse:stripe",
    "lever:palantir",
    "ashby:ramp"
  ]
}' |
apify call brightish_ascent/career-site-jobs-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,brightish_ascent/career-site-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/BHJUp6879tK9x1vma/builds/dGQ1gRR0yVGfvwJPN/openapi.json