# Hiring Intent Monitor — New Job Postings Watcher (`dev-hoss/hiring-intent-monitor`) Actor

Watch company career pages and get only NEW job postings since the last run. Detects Greenhouse, Lever, Ashby, Workable and SmartRecruiters boards via their APIs, with a generic HTML fallback. A hiring-intent sales signal for B2B teams and AI agents.

- **URL**: https://apify.com/dev-hoss/hiring-intent-monitor.md
- **Developed by:** [Hossam Mohamed](https://apify.com/dev-hoss) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 16.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 company checkeds

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Hiring Intent Monitor — New Job Postings Watcher

Watch a list of company career pages and get **only the NEW job postings since your last run**. A hiring-intent sales signal: companies that are hiring are growing, spending, and buying — reach out while the role is open.

### How it works

1. For each company you list, the Actor finds the careers page.
2. If the company uses a supported ATS (**Greenhouse, Lever, Ashby, Workable, SmartRecruiters**), postings come straight from the ATS board API — exact titles, locations, departments.
3. Otherwise it parses posting links from the career site's HTML (up to `maxCareersPages` pages).
4. Every posting is diffed against the watchlist state, so each run emits **only what's new**. Postings stay in state until they close (or `forgetAfterDays` passes).

### Quick start

```json
{
    "companies": ["stripe.com", "vercel.com", "anthropic.com"],
    "firstRunReportsAll": false
}
```

Run 1 records the baseline (no noise). Run 2 onward reports only genuinely new postings.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `companies` | array (required) | — | 1–200 domains or URLs. A URL with a path (e.g. `https://acme.com/careers`) is used as the careers-page hint. |
| `maxCareersPages` | integer | `3` | Career-site pages fetched per company for non-ATS sites. |
| `concurrency` | integer | `5` | Companies checked in parallel. |
| `forgetAfterDays` | integer | `120` | Drop postings from state after this many days. |
| `stateKey` | string | `default` | Use different keys for separate watchlists in one Actor. |
| `firstRunReportsAll` | boolean | `false` | Seed run: report all current postings as new (build a lead list fast). |
| `proxyConfiguration` | object | off | Optional proxy. Career pages and ATS APIs are public — rarely needed. |

### Output

**Default dataset — `new-posting`, one per new job posting** (this is the sales-signal feed):

```json
{
    "type": "new-posting",
    "company": "vercel.com",
    "title": "Senior Software Engineer, Databases",
    "url": "https://jobs.ashbyhq.com/vercel/abc123",
    "location": "Remote",
    "department": "Engineering",
    "source": "ashby",
    "careersUrl": "https://vercel.com/careers",
    "postedAt": "2026-09-02",
    "firstSeenAt": "2026-09-05T10:00:00.000Z"
}
```

Unreachable companies produce `type: "error"` records in the same dataset.

**`type: domain-summary` records in the same dataset — one per company** (coverage report): careers URL found, ATS detected, total open postings, new count, first-run flag, check timestamp. Filter by `type` (e.g. the New postings / Coverage tabs in Console).

Scheduling tip: create a **task** with your watchlist and schedule it **daily or weekly** — each run then contains exactly the fresh postings since the last one, ready for webhooks/API consumption.

### How much does it cost?

Pay per event: a small fee per company checked (the monitoring itself) plus a fee per new posting found (the signal itself). Companies on supported ATS boards resolve in one API call, so runs are fast and cheap. Compare: hiring-intent data providers charge $100+/month for the same signal.

### Who is this for?

- **B2B sales / GTM teams** — hiring roles in your ICP = buying intent; reach out with a relevant angle
- **Recruiters** — monitor client/prospect companies for new openings
- **Investors & analysts** — track hiring velocity across a portfolio or sector
- **AI agents** — structured JSON, stable schemas, one record per signal, `run-sync` friendly

### Use with AI agents

Built for agents: documented JSON input schema, one stable record per signal, no auth beyond the caller's own Apify token. The simplest integration is the run-sync endpoint, which starts the run and returns new postings in one call:

```
POST https://api.apify.com/acts/dev-hoss~hiring-intent-monitor/run-sync-get-dataset-items?token=YOUR_API_TOKEN
Content-Type: application/json

{"companies": ["stripe.com", "vercel.com"], "stateKey": "agent-watchlist"}
```

It also works with Apify's hosted MCP server (`mcp.apify.com`) — add the Actor to your MCP client and the input schema drives the tool call. Tip for agents: keep a persistent `stateKey` per watchlist so every call returns only genuinely new postings.

# Actor input Schema

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

Company domains or URLs to monitor, e.g. \["stripe.com", "https://vercel.com/"]. On every run the Actor checks each company's career page and reports only NEW postings since the previous run. Maximum 200 companies per run.

## `maxCareersPages` (type: `integer`):

How many career-site pages are fetched per company when the site does not use a supported ATS (Greenhouse, Lever, Ashby, Workable, SmartRecruiters). ATS-backed companies always resolve in a single API call.

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

How many companies are checked in parallel.

## `forgetAfterDays` (type: `integer`):

Postings that stay open longer than this are dropped from state, so if they close and reopen they are reported as new again. Keep this longer than your typical posting duration.

## `stateKey` (type: `string`):

Key-value store key used to remember known postings between runs. Use different keys to monitor separate watchlists (e.g. 'europe' vs 'us') in the same Actor.

## `firstRunReportsAll` (type: `boolean`):

If enabled, the very first run for a company reports all current postings as new (useful to seed a lead list). If disabled, the first run only records the baseline and reports nothing.

## `proxyConfiguration` (type: `object`):

Optional proxy settings. Usually not needed — career pages and ATS APIs are public.

## Actor input object example

```json
{
  "companies": [
    "stripe.com",
    "vercel.com"
  ],
  "maxCareersPages": 3,
  "concurrency": 5,
  "forgetAfterDays": 120,
  "stateKey": "default",
  "firstRunReportsAll": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `newPostings` (type: `string`):

One record per job posting that was not present on the previous run: company, title, URL, location, department and source (ATS or HTML).

# 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": [
        "stripe.com",
        "vercel.com"
    ],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("dev-hoss/hiring-intent-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": [
        "stripe.com",
        "vercel.com",
    ],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("dev-hoss/hiring-intent-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": [
    "stripe.com",
    "vercel.com"
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call dev-hoss/hiring-intent-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dev-hoss/hiring-intent-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/NuV6L9V4nP2OZ6kX4/builds/BJgZouQDpHHNOwybL/openapi.json