Company Hiring Monitor: Lever Job Openings & Changes

Get current public jobs for companies using Lever, plus new and closed postings since the previous successful check. Use hiring signals for account research, recruiting, job alerts, or market monitoring. No Lever account, API key, login, or proxy is needed.

Input

{
  "companies": ["palantir", "https://jobs.eu.lever.co/example-company"],
  "monitorId": "daily"
}

Supply 1–500 unique company slugs or exact HTTPS board URLs on jobs.lever.co or jobs.eu.lever.co. Slugs are lowercased and deduplicated; they must match ^[a-z0-9][a-z0-9._-]{0,99}$. Invalid input rejects the run before collection or billing. URLs with credentials, ports, queries, fragments, or extra path segments are rejected.

monitorId defaults to default and must match ^[a-z0-9-]{1,40}$. Reuse the same ID to compare runs. Different IDs create independent monitors. The prefill palantir was checked against the public API on October 15, 2026 and returned 314 openings; counts change over time.

Output

One dataset item per company. This illustrative first-check result shows one posting:

{
  "company": "example-company",
  "source": "lever",
  "boardUrl": "https://jobs.lever.co/example-company",
  "status": "ok",
  "checkedAt": "2026-10-15T12:00:00.000Z",
  "openCount": 1,
  "summary": {
    "byTeam": { "Engineering": 1 },
    "byDepartment": { "Product": 1 },
    "byLocation": { "Remote": 1 },
    "byCommitment": { "Full-time": 1 },
    "byWorkplaceType": { "remote": 1 }
  },
  "postings": [{
    "id": "example-id",
    "title": "Software Engineer",
    "team": "Engineering",
    "department": "Product",
    "location": "Remote",
    "commitment": "Full-time",
    "workplaceType": "remote",
    "createdAt": "2026-10-14T09:00:00.000Z",
    "url": "https://jobs.lever.co/example-company/example-id"
  }],
  "changes": {
    "firstCheck": true,
    "previousCheckedAt": null,
    "opened": [],
    "closed": []
  }
}

source is lever or lever-eu. opened contains complete postings whose IDs were absent last time. closed contains the previous id, title, and url for IDs that disappeared. A title change on the same ID is not an opening or closure. The first successful check establishes the baseline and reports no changes.

Snapshots persist in the named key-value store hiring-monitor-state-<monitorId>, one key per normalized company. Only successful, delivered checks update them. Timeouts, invalid or incomplete responses, and missing boards preserve the previous snapshot and report empty change arrays. previousCheckedAt points to the last successful check, even after failed runs. Without any snapshot, firstCheck remains true.

Schedule this Actor daily with the same monitorId to receive changes. Run a given monitor sequentially: overlapping runs with the same ID can race when updating its store. Keep the named store to retain history between runs. The dataset contains each run's results; the named store holds only the latest successful snapshot.

Pricing

US$10 per 1,000 successfully checked companies (US$0.01 per company-checked event). You are charged only when the check succeeds, including a valid board with zero openings. not_found and error results are returned to the dataset without this event charge. Apify platform costs, if applicable to your plan, are separate.

The event is charged before data is added to the dataset. If the spending limit is reached, the Actor stops; a successful report that was not charged is not delivered and does not advance the snapshot.

Limits and interpretation

• Lever only, including its global and EU instances. A global 404 triggers an EU lookup. Other ATS providers are unsupported.
• At most 500 unique companies per run, processed sequentially; at most one API request per second across pagination, fallback, and companies. Large runs take longer.
• Public postings only. Each page requests 100 postings; collection continues until a shorter page arrives. A 15-second deadline per request, 4 MB per page, or the 1,000-page safety ceiling produces a free error without replacing state. Duplicate IDs also invalidate the collection.
• Lever does not provide an atomic snapshot across pages. Board changes during collection can affect the observed result. Disappearance means a posting left the public API, and does not establish that a candidate was hired.
• Missing category fields are empty strings and count under unspecified in summaries. Creation timestamps are ISO formatted. A missing or invalid creation timestamp invalidates the check, preserving state without charging the event.
• Network traffic for collection is restricted to api.lever.co and api.eu.lever.co; redirects are refused. No arbitrary websites are fetched.

Source: Lever Postings API documentation.