# Career Page Job Monitor - Track Company Hiring (`midnight_static/career-page-job-monitor`) Actor

Watch the companies you choose and get what changed: NEW, CHANGED and CLOSED roles from their Greenhouse and Lever job boards. Hiring signal tracking for recruiters, sales and competitive intelligence. 26 fields per job. Charged per company, not per job.

- **URL**: https://apify.com/midnight\_static/career-page-job-monitor.md
- **Developed by:** [Midnight Static](https://apify.com/midnight_static) (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 $7.00 / 1,000 career pages

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

## Career Page Job Monitor

Give it the companies you care about. It reads their Greenhouse and Lever career pages and tells you **what changed since last time**: which roles are new, which were edited, which disappeared.

### Four things that are different here

**1. It returns a diff, not a firehose.**
Every job carries a `changeStatus`: `NEW`, `CHANGED`, `CLOSED` or `UNCHANGED`. The second run on an unchanged board reports zero new roles — and costs the same as the first, because you pay per company, not per row. Most job APIs hand you the same 600 rows every morning and let you work out what moved.

**2. You pay per company, not per job.**
$0.01 per company checked. A company with 600 open roles costs the same as one with 3. A company that cannot be reached, does not exist, or is blocked by `robots.txt` is reported in the run statistics and **costs nothing**.

**3. `CLOSED` is a first-class result.**
A role vanishing is often the signal you actually wanted: the seat got filled, the req got cut, the team stopped growing. Jobs that were open last run and are gone now come back as `CLOSED` rows. Nothing else has to remember for you.

**4. The coverage list is short on purpose, and the reasons are published.**
Two ATS platforms are supported: **Greenhouse** and **Lever**. Two more were tested and rejected — see *Limits and compliance*. Naming what is missing is more useful than a long list that quietly returns nothing.

### What you get

**The role**
Job id, title, company, company slug, ATS, direct link, location, offices, departments or team, requisition id, internal job id, language.

**Timing**
First published, last updated by the employer, application deadline where the employer sets one, and `daysOpen` — how long the role has been live. A role open for 90 days says something different from one posted yesterday.

**The description**
Full posting text as clean plain text, tags and HTML entities resolved, plus `descriptionLength` — the true length before truncation, not the truncation limit.

**Change tracking**
`changeStatus`, `firstSeenAt`, `checkedAt`.

**Extras where the ATS exposes them**
Greenhouse: GDPR consent flag and AI disclaimer. Lever: workplace type (remote / hybrid / onsite), country, commitment (full-time, contract).

### Typical uses

Recruiters watching target accounts and wanting to be first to a new req. Sales teams using hiring as a buying signal — a company posting five backend roles is scaling. Competitive intelligence: which team is a rival growing, in which city. Anyone building a niche job board from a curated company list.

### Example record (trimmed)

```json
{
  "changeStatus": "NEW",
  "title": "Account Executive, EMEA (Germany)",
  "companyName": "Webflow",
  "ats": "greenhouse",
  "locationName": "London, U.K. (Hybrid)",
  "departments": ["Sales"],
  "firstPublishedAt": "2026-08-05T08:51:57.000Z",
  "updatedAt": "2026-08-10T19:24:15.000Z",
  "daysOpen": 44,
  "descriptionLength": 8185,
  "gdprConsentRequired": false,
  "jobUrl": "https://job-boards.greenhouse.io/webflow/jobs/7951430"
}
```

### Input

Paste a career page URL — `https://boards.greenhouse.io/COMPANY` or `https://jobs.lever.co/COMPANY` — or the short form `greenhouse:COMPANY` / `lever:COMPANY`. A link to a single job works too; the company is read out of it. Duplicates collapse and are charged once.

`onlyChanged` writes only `NEW`, `CHANGED` and `CLOSED` rows. `reportClosed` turns the closed-role rows off. `maxCompanies` caps how many companies are charged; the default of 100 costs $1.00.

### Failures are loud

Counters are reconciled at the end of every run: companies processed must equal companies charged plus companies skipped, and the run **fails** if they do not. If a provider returns HTTP 200 but not the payload shape we expect, the run fails with the affected companies named rather than silently writing an empty dataset. The breakdown goes to `RUN_STATS`, every skipped company with its reason to `SKIPPED`.

A company that could not be reached this run keeps its remembered state, so a temporary network error does not make every role look `NEW` next time.

### Limits and compliance

`robots.txt` is read for each provider before any request and the gate is fail-closed.

**Two platforms were tested and left out, measured on 18 September 2026:**

- **Ashby** — the endpoint works and returned 147 jobs in one request, but `api.ashbyhq.com/robots.txt` answers **HTTP 401**. Our rule is that an unreadable `robots.txt` means no request, so Ashby is out until that changes.
- **Workable** — the public widget endpoint was tried against 13 companies. Twelve returned HTTP 200 with an **empty** jobs array. The endpoint no longer returns postings, so it is not shipped as if it did.

**No personal data is collected.** Job postings are company records, not people. The ATS payloads were scanned for recruiter names, e-mail addresses and phone numbers across 94 live postings: none present. Output is built from a published field list.

### Pricing

**$0.01 per company checked, everything included.** No start fee, no minimum charge per run, no separate platform usage line.

Paid Apify plans pay less, automatically — there is nothing to apply for: Bronze $0.009, Silver $0.008, Gold and above $0.007 per company. The Free plan price is unchanged at $0.01.

Jobs are written free of charge, however many a company has.

### Measured performance

Run on 18 September 2026:

| | |
|---|---|
| Companies checked | 3 |
| Jobs returned | 94 (27 + 13 + 54) |
| Fields populated per job | 17 of 26 (median) |
| Tags or HTML entities left in description text | 0 of 94 |
| Personal data found | none |
| Change detection: no-op second run | 0 new, 0 changed, 94 unchanged |
| Change detection: one edit, one removal, one addition | 1 `NEW`, 1 `CHANGED`, 1 `CLOSED`, 92 unchanged |
| Densest single request | 668 jobs (Greenhouse, measured separately) |

**Known limit:** company slugs cannot be discovered automatically. Greenhouse publishes no board directory and guessing slugs from company names hit **2 of 25** in a measured test. That is why you supply the list — and why you are never charged for a guess that misses.

# Actor input Schema

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

One company per line. Paste the career page URL — https://boards.greenhouse.io/COMPANY or https://jobs.lever.co/COMPANY — or use the short form greenhouse:COMPANY / lever:COMPANY. A link to a single job works too; the company is read from it. Duplicates are collapsed and charged once.

## `onlyChanged` (type: `boolean`):

On by default after the first run in most workflows: writes only NEW, CHANGED and CLOSED rows and leaves out everything that stayed the same. Turn off to get the full current list of openings every run. Either way you are charged per company, not per row.

## `reportClosed` (type: `boolean`):

Write a CLOSED row for a job that was open in the previous run and is gone now. A role disappearing is often the signal you want.

## `maxCompanies` (type: `integer`):

Hard cap on how many companies are checked and charged, so a long list cannot produce an unexpected bill. The default of 100 costs $1.00.

## `concurrency` (type: `integer`):

How many companies are checked in parallel.

## Actor input object example

```json
{
  "companies": [
    "https://boards.greenhouse.io/webflow",
    "https://jobs.lever.co/ro",
    "greenhouse:planetscale"
  ],
  "onlyChanged": false,
  "reportClosed": true,
  "maxCompanies": 100,
  "concurrency": 4
}
```

# Actor output Schema

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

One row per job, each tagged NEW, CHANGED, CLOSED or UNCHANGED against the previous run.

## `runStats` (type: `string`):

Counters: companies processed and charged, jobs seen, new, changed, closed, unchanged, plus every failure class.

## `skipped` (type: `string`):

Every company that could not be checked, with the reason. Free, never charged.

# 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": [
        "https://boards.greenhouse.io/webflow",
        "https://jobs.lever.co/ro",
        "greenhouse:planetscale"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("midnight_static/career-page-job-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": [
        "https://boards.greenhouse.io/webflow",
        "https://jobs.lever.co/ro",
        "greenhouse:planetscale",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("midnight_static/career-page-job-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": [
    "https://boards.greenhouse.io/webflow",
    "https://jobs.lever.co/ro",
    "greenhouse:planetscale"
  ]
}' |
apify call midnight_static/career-page-job-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,midnight_static/career-page-job-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/DmPKvyM6WXzqlarNe/builds/RcH8RC2YQ0JAh7tGv/openapi.json