# Company Jobs Scraper | Hiring Change Feed (`danthedataman/company-hiring-ledger`) Actor

Export jobs from Greenhouse, Lever, Ashby and Workable career pages. Filter by title, location or remote status; compare full snapshots with safeguards for closed-job rows.

- **URL**: https://apify.com/danthedataman/company-hiring-ledger.md
- **Developed by:** [Eli J](https://apify.com/danthedataman) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.57 / 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.
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

### What you can export

Use this **company jobs and careers-page scraper** for hiring research and alerts. Supply company domains, careers pages or supported Greenhouse, Lever, Ashby and Workable board URLs to export published openings and available job details.

Filter by title, location or published remote status. Compare a full prior snapshot to emit new, changed and observed-closed jobs; incomplete reads suppress closure inferences.

### Try the shipped prefill

Use the input form's example values for a first run. Prefills are examples, not API defaults; check the billing and limits before starting.

```json
{
  "companies": [
    "https://job-boards.greenhouse.io/practicebetter",
    "https://jobs.ashbyhq.com/onhires"
  ],
  "maxJobsPerCompany": 2
}
```

### Input

| Field | Type | Default | Description |
| --- | --- | --- | --- |
| `companies` | array | none | Company domains, careers URLs or direct supported ATS board URLs. Required; omitted or `[]` is refused at start. Null makes no requests. |
| `titleKeywords` | array | `[]` | Case-insensitive title substrings; any keyword may match. Null means no filter. |
| `locationText` | string | empty | Case-insensitive substring in any published location; null means no filter. |
| `remoteOnly` | boolean | `false` | Keep only jobs explicitly published as remote. Null means false; unknown remote status does not match. |
| `maxJobsPerCompany` | integer | `100` | Nonnegative cap on matched current jobs read and total rows delivered per distinct board. Null means 100; zero makes no requests. |
| `baselineDatasetId` | string | none | Optional read-only full snapshot dataset. Its presence enables monitor mode. |

Filters combine: title AND location AND remote. Duplicate inputs and boards
are exported once. The example prefill reads two jobs per board from two ATS
families; it is a starting example, not an API default.

Omitting `companies` (including `{}`) or sending `[]` is refused before any run or charge.
With other inputs valid, null succeeds with guidance and no rows; Actor Start still applies.
No job rows means no dataset-item event; the platform may apply an Actor Start
event according to the listing's pricing. Jobs are billed per 1,000 job rows.
The Actor stops all further reads when the customer's maximum charge binds.

### Job rows

One row is one job. Missing source fields are null; multiple locations remain
an array. Source prose and structured compensation are preserved without
currency conversion, annualization or inferred pay. Structured salary values
carry the source's currency and period when given. Compensation text retains
source lines that explicitly name salary, compensation or base pay and a
currency. Other pay wording can remain only in the full description.

| Field | Meaning |
| --- | --- |
| `company` | Source company name for Greenhouse/Workable; exact board token for Lever/Ashby, whose feeds do not publish a company name. |
| `atsFamily` | `greenhouse`, `lever`, `ashby` or `workable`. |
| `boardToken` | Board identifier from an observed URL; Ashby uses canonical lowercase identity. |
| `jobId` | Source stable job id, or Workable shortcode, as a string. Identity is `(atsFamily, boardToken, jobId)`. |
| `title` | Published job title. |
| `department` / `team` | Published department and team, when present. |
| `locations` | Published location names; Workable city, region and country joined without geocoding. |
| `remote` | Boolean when explicitly published; Greenhouse location names containing “remote” give true, otherwise null. Hybrid/onsite Lever values give false. |
| `employmentType` | Published employment type; no inference from description. |
| `compensation` | Null or an object with `structured` (raw salary range/tiers) and `text` (exact extracted source text lines). Greenhouse pay-enabled details are read for matched jobs. |
| `postedAt` / `updatedAt` | Published absolute timestamps/dates; Lever epoch milliseconds become UTC ISO timestamps. Unknown values are null. |
| `applyUrl` | Published application URL; Greenhouse supplies the job's application landing. |
| `description` | Job description as text, including Lever lists and additional sections. |
| `sourceUrl` | Published job-page URL. |
| `scrapedAt` | UTC collection timestamp. |
| `changeStatus` | Monitor mode only: `new`, `changed` or `closed`. |
| `changedFields` | Changed rows only: sorted names of changed normalized content fields. Collection time is excluded. |

Download JSON, CSV or Excel from the default dataset. Output links expose job
rows and the ERRORS key-value record. No job applications are submitted.

### Monitor jobs

First run without a baseline to make a full snapshot. Select its dataset in
`baselineDatasetId` on a later run, using the same company boards and filters.
Use a job limit large enough to read those boards completely. The baseline is
never changed. Empty baselines are accepted with a warning and make all current jobs new. Unchanged jobs emit
no row. Closed jobs copy their last known source content with a fresh
`scrapedAt` and `changeStatus: "closed"`.
Closed rows are reported only when their last known content matches the current filters.

Closed jobs are emitted only when that company's current board is completely
read. Failed pages/details, malformed rows, duplicates during pagination and
truncated reads suppress closures. Workable closures additionally require the
public board count to match the returned job identities; a failed count or
mismatch suppresses closures. Jobs excluded by current filters remain present
for closure checks; changing a filter never proves a job closed.
No baseline company absent from this run is marked closed. A complete empty
board may close previous jobs. The baseline must come from a full snapshot run.
Rows carrying `changeStatus` are rejected. An empty dataset cannot reveal its
mode from its rows; do not select an empty monitor delta, as every current job
would then be new. Keep the original snapshot or make a new full snapshot for
the next comparison. This is a comparison of two observations,
not a historical feed of intermediate job changes.

Baseline resource selection requests only `READ` under `LIMITED_PERMISSIONS`.
Apify's [Actor permissions](https://docs.apify.com/platform/actors/development/permissions#access-user-provided-storages)
contract says Actors can access storages “users explicitly provide via the
Actor input” and the run token permits only the requested operations.

### Supported boards and limits

- Greenhouse: `job-boards.greenhouse.io/<token>` and `boards.greenhouse.io/<token>`.
- Lever: `jobs.lever.co/<token>`; offset pages are read until an empty page or the job cap.
- Ashby: `jobs.ashbyhq.com/<token>`; only listed jobs are exported.
- Workable: `apply.workable.com/<token>`; `/j/<shortcode>` alone is a job shortlink, not a company board.

Custom job portals, SmartRecruiters, Workday and iCIMS are outside this Actor's
supported list. Unsupported inputs go to ERRORS. Some employers publish pay
only in prose or omit employment type and dates. Direct anonymous HTTP is
used; no login, browser or proxy is required by the measured feed contracts.
Live boards can change during a read, so even a completed traversal is an
observation rather than an atomic snapshot. Partial failures retain valid
rows; an all-attempts-failed run fails with guidance. Input/baseline errors
fail before company requests.

# Changelog

This Actor's version history is a separate document: https://apify.com/danthedataman/company-hiring-ledger/changelog.md

# Actor input Schema

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

Domains, careers-page URLs or direct supported ATS board URLs. Omitted or \[]: Apify refuses the start, with no run or charge. With other inputs valid, null succeeds with guidance and no requests or rows; Actor Start still applies. Provide direct board URLs when discovery cannot resolve a company.

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

Case-insensitive title substrings; match any keyword. Omitted, null or \[] means no title filter.

## `locationText` (type: `string`):

Case-insensitive substring in any published location. Omitted, null or empty means no location filter.

## `remoteOnly` (type: `boolean`):

Include only jobs explicitly published as remote. Unknown remote flags do not match. Omitted or null means false.

## `maxJobsPerCompany` (type: `integer`):

At most this many matched current jobs per board; also caps delivered rows per board. Omitted or null means 100. Zero makes no requests. A capped read suppresses closed jobs.

## `baselineDatasetId` (type: `string`):

Optional previous full snapshot dataset. When supplied, export only new, changed and closed jobs. Read only; no write to the baseline. Use the same companies, filters and a sufficiently large job limit for successive snapshots. Closed jobs require a complete current board read.

## Actor input object example

```json
{
  "companies": [
    "https://job-boards.greenhouse.io/practicebetter",
    "https://jobs.ashbyhq.com/onhires"
  ],
  "maxJobsPerCompany": 2
}
```

# Actor output Schema

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

No description

## `errors` (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 = {
    "companies": [
        "https://job-boards.greenhouse.io/practicebetter",
        "https://jobs.ashbyhq.com/onhires"
    ],
    "maxJobsPerCompany": 2
};

// Run the Actor and wait for it to finish
const run = await client.actor("danthedataman/company-hiring-ledger").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://job-boards.greenhouse.io/practicebetter",
        "https://jobs.ashbyhq.com/onhires",
    ],
    "maxJobsPerCompany": 2,
}

# Run the Actor and wait for it to finish
run = client.actor("danthedataman/company-hiring-ledger").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://job-boards.greenhouse.io/practicebetter",
    "https://jobs.ashbyhq.com/onhires"
  ],
  "maxJobsPerCompany": 2
}' |
apify call danthedataman/company-hiring-ledger --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,danthedataman/company-hiring-ledger"
        }
    }
}
```

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/LdjK7efZsC8Wjceun/builds/Bbeyw2DeUD0uAtwcK/openapi.json