# Job Board Monitor (`yearly_register/job-board-monitor`) Actor

Monitor public job boards and career pages, extract normalized vacancies, and schedule repeat checks for new roles and hiring signals.

- **URL**: https://apify.com/yearly\_register/job-board-monitor.md
- **Developed by:** [Automation Tech](https://apify.com/yearly_register) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 job results

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?

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

## Job Board Monitor

Job Board Monitor extracts stable job listings from public job pages using JobPosting structured data when available or explicit CSS selectors for supported custom extraction. It is designed for repeatable monitoring of public vacancies and produces normalized dataset records that are easier to filter, compare, and automate against than raw pages.

### What it does

The Actor crawls configured job-board or career-page URLs, extracts supported listing data, normalizes each job, and writes the results to the default Apify dataset. Structured JobPosting data is preferred where available because it usually survives visual redesigns better than page selectors.

Typical use cases include:

- monitoring new vacancies from selected employers;
- tracking jobs in a niche or location;
- collecting public job data for internal research;
- feeding new listings into alerts or downstream workflows;
- scheduling recurring job-board checks in Apify.

### Quick start

1. Add one or more supported public job or career-page URLs.
2. Keep request and result limits low for the first run.
3. Run the Actor and inspect the default dataset.
4. Confirm that titles, links, company/location information, and other available fields are being normalized as expected.
5. Configure selector-based extraction only when the target does not provide usable structured JobPosting data.
6. Schedule the Actor or call it through the Apify API once the source is verified.

The Input tab also provides limits, retries, concurrency, timeout, and proxy controls.

### Output

Each dataset item represents a normalized public job listing with source and scrape metadata. The dataset schema defines the exact contract. Results can be exported as JSON, CSV, or Excel or consumed through the Apify dataset API.

### Scheduling and integrations

Scheduled runs are useful for finding newly published vacancies without repeatedly checking pages manually. Connect the dataset to webhooks, Make, Zapier, a database, a notification service, or another Actor.

### Limitations

Career sites vary significantly. Structured data may be incomplete, and selector-based extraction can break when a target changes its markup. Some sites load listings behind authentication, JavaScript applications, geo restrictions, or anti-bot systems that this Actor may not support. Verify each source before relying on it for critical hiring data.

### Pricing

The currently configured pricing model and rates are shown in the Actor's Apify Store **Pricing** tab. Platform cost depends on page count, run frequency, retries, proxy use, and source complexity. Test a small representative input before enabling a large recurring monitor.

# Actor input Schema

## `startUrls` (type: `array`):

List of URLs to start scraping from

## `maxResults` (type: `integer`):

Maximum number of results to scrape

## `maxRequests` (type: `integer`):

Maximum number of requests to process

## `maxConcurrency` (type: `integer`):

Maximum number of concurrent requests

## `maxRequestRetries` (type: `integer`):

Maximum number of retries for failed requests

## `maxRequestsPerMinute` (type: `integer`):

Maximum requests per minute

## `requestTimeoutSecs` (type: `integer`):

Request timeout in seconds

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

Proxy configuration for requests

## `debug` (type: `boolean`):

Enable debug logging

## `jobSelector` (type: `string`):

CSS selector for repeated job containers. Empty uses JobPosting JSON-LD only.

## `titleSelector` (type: `string`):

CSS selector for the job title within each container.

## `companySelector` (type: `string`):

CSS selector for the company name within each container. Empty leaves the company unknown.

## `locationSelector` (type: `string`):

CSS selector for explicit location text within each container.

## `linkSelector` (type: `string`):

CSS selector for the job link within each container.

## `dateSelector` (type: `string`):

CSS selector for the posting date; reads datetime or content before visible text.

## `descriptionSelector` (type: `string`):

CSS selector for the description within each container. Empty emits an empty description.

## `maxJobsPerPage` (type: `integer`):

Maximum number of valid titled jobs returned from each page.

## `maxDescriptionLength` (type: `integer`):

Maximum description characters to emit; the hash always covers the full normalized text.

## Actor input object example

```json
{
  "startUrls": [],
  "maxResults": 1000,
  "maxRequests": 10000,
  "maxConcurrency": 10,
  "maxRequestRetries": 3,
  "maxRequestsPerMinute": 60,
  "requestTimeoutSecs": 30,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "debug": false,
  "jobSelector": "",
  "titleSelector": "h1, h2, h3",
  "companySelector": "",
  "locationSelector": "",
  "linkSelector": "a[href]",
  "dateSelector": "",
  "descriptionSelector": "",
  "maxJobsPerPage": 100,
  "maxDescriptionLength": 10000
}
```

# Actor output Schema

## `results` (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 = {
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("yearly_register/job-board-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 = { "proxyConfiguration": { "useApifyProxy": False } }

# Run the Actor and wait for it to finish
run = client.actor("yearly_register/job-board-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 '{
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call yearly_register/job-board-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,yearly_register/job-board-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/1pVUtHXyR14ciNH1W/builds/Hm6S2r8Ehg8pOS10o/openapi.json