# LinkedIn Jobs - New, Changed And Quietly Closed Roles (`reapx/linkedin-jobs-monitor`) Actor

Know which roles are new, which quietly changed and which closed without anyone saying so - so you reach the hiring manager while the job is still open.

- **URL**: https://apify.com/reapx/linkedin-jobs-monitor.md
- **Developed by:** [Tarek Etman](https://apify.com/reapx) (community)
- **Categories:** Jobs, Business, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.40 / 1,000 job posting monitoreds

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/platform/actors/running/actors-in-store#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

![reapX - the record of what changed](https://reapx.dev/reapx.gif)

## LinkedIn Jobs Monitor - New, Changed & Closed Roles

> "That role was open for two months, then vanished. Did they hire, or did they give up?"

Job boards only show what is currently open, so the underlying hiring story is deleted as it happens. Recruitment teams, sales reps, and competitive strategy teams need to track job postings as they appear, change, and close to read market signals accurately.

Track job postings over time as they appear, change, and close, emitting active days open, repost flags, and modified fields mapped to stable `jobId` identifiers.

### ⬇️ Input

The actor accepts job search query objects specifying keywords and location filters.

| Field | Type | Description |
|---|---|---|
| `queries` | Array | List of search query objects containing keywords and location filters. |
| `maxItems` | Integer | Maximum number of job postings to fetch in a single run. |
| `proxyConfiguration` | Object | Proxy settings to rotate IPs per request. |

### ⬆️ Output

Outputs structured records directly to the default dataset. Each row describes a single job posting indexed by its stable per-row identifier (`jobId`).

- `jobId` (Numeric LinkedIn job posting ID)
- `daysOpen` (Active days open across observed runs)
- `closedWithoutRepost` (Flag indicating role closed without being reposted)
- Derived status and modified field attributes.

### How it works

1. **Job Extraction**: Queries LinkedIn guest job search endpoints without login requirements.
2. **Card Parsing**: Extracts posting ID, title, company, location, salary text, and posting timestamps.
3. **Change Tracking**: Compares postings across repeated runs to calculate active days open and detect closed or modified listings.
4. **Resilient Rate Budgeting**: Integrates proxy rotation to prevent rate limiting and ensure stable data streams.

### ❓ FAQ

#### How does job closure tracking work?

By monitoring job IDs across sequential runs, the actor detects when a posting disappears from search results, marking its closure date and calculating total active days open.

#### Why do daysOpen and closedWithoutRepost return null on first run?

Tracking how long a role stays open requires observing the posting over time across multiple runs. On the first run, the actor returns `null` with a clear `reason` field rather than guessing.

### 💬 Your feedback

Need custom role filters, company tracking lists, or dataset integrations? Contact reapxdev@proton.me.

***

*Unofficial - not affiliated with LinkedIn. Collects only data visible without logging in.*
reapx · reapx.dev · reapxdev@proton.me

# Actor input Schema

## `queries` (type: `array`):

The searches you want watched - a job title, or a title and a location together. Each one gets tracked, so you see what changed between runs.

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

How many postings come back across all your searches. Raise it when you are covering a whole market rather than one title.

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

How the run reaches the platform. The default is already the route that works for this source, so leave it alone unless you have a reason to change it.

## Actor input object example

```json
{
  "queries": [
    {
      "keywords": "software engineer",
      "location": "United States"
    }
  ],
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `items` (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 = {
    "queries": [
        {
            "keywords": "software engineer",
            "location": "United States"
        }
    ],
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("reapx/linkedin-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 = {
    "queries": [{
            "keywords": "software engineer",
            "location": "United States",
        }],
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("reapx/linkedin-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 '{
  "queries": [
    {
      "keywords": "software engineer",
      "location": "United States"
    }
  ],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call reapx/linkedin-jobs-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,reapx/linkedin-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/yoic3orw08XKqdPXd/builds/oksYtvggfQx9KdSJh/openapi.json