# hiring-signals-pro (`wheresprada/hiring-signals-pro`) Actor

Extract public job listings from Greenhouse and Lever career boards. Get job titles, companies, locations, departments, direct job URLs, clean role descriptions, and salary ranges when available. Filter by job title or location, exclude recruitment events, and export structured data.

- **URL**: https://apify.com/wheresprada/hiring-signals-pro.md
- **Developed by:** [Mahruf Hossain](https://apify.com/wheresprada) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

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

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

## Hiring Signals Pro — Greenhouse & Lever Job Listings

Extract structured job listings from public **Greenhouse** and **Lever** career boards. Select the employers you want to scan, filter by job title or location, and download a clean dataset with direct links to the original postings.

Use Hiring Signals Pro for recruitment research, talent-market research, sales prospecting based on public hiring activity, or job-data workflows.

### What you get

Each matching listing is delivered as one record in the run's default dataset, with these fields:

| Field | Description |
| --- | --- |
| `company`, `title` | Employer label and position title |
| `location`, `department` | Location and team/department, where supplied |
| `employmentType`, `workplaceType` | Employment arrangement and workplace type, when available |
| `salaryText` | Published salary range, when clearly available |
| `jobUrl` | Direct link to the employer's posting |
| `source`, `jobId` | ATS provider and unique provider-based listing ID |
| `firstPublishedAt` | Provider-reported posting timestamp, when available |
| `descriptionExcerpt` | Clean, plain-text job description preview (up to 450 characters) |
| `checkedAt` | Timestamp of this scan |

Empty fields indicate that information was not available or could not be reliably extracted. Salaries, timestamps and job-type details are **not guaranteed** for every employer or posting.

### How to use

1. Open the **Input** tab and specify one or more supported career boards.
2. For each board, choose `greenhouse` or `lever`, enter the company's board **slug/token** in `site`, and give it a readable `company` label. Do **not** enter a full URL as the site.
3. Optionally set `titleKeywords`, `locationKeywords`, `maxResults`, and `includeRecruitmentEvents`.
4. Click **Start**. Once the run finishes, open the **Output** tab to view or export the results as JSON, CSV or another available dataset format.

#### Example input

```json
{
  "boards": [
    {"platform": "lever", "site": "h1", "company": "H1", "region": "global"},
    {"platform": "greenhouse", "site": "imc", "company": "IMC", "region": "global"}
  ],
  "maxResults": 50,
  "includeRecruitmentEvents": false,
  "titleKeywords": [],
  "locationKeywords": []
}
```

These are example employer boards, not a fixed employer list. You can supply your own public Greenhouse or Lever boards. For a URL such as `https://jobs.lever.co/h1`, the Lever `site` is `h1`; for `https://job-boards.eu.greenhouse.io/imc`, the Greenhouse `site` is `imc`.

#### Input options

| Setting | How it works |
| --- | --- |
| `boards` | 1–10 public Greenhouse/Lever boards per run |
| `maxResults` | Maximum number of output records, 1–1,000 (default 100) |
| `titleKeywords` | Match **any** supplied phrase against the job title, case-insensitively |
| `locationKeywords` | Match **any** supplied phrase against the location, case-insensitively |
| `includeRecruitmentEvents` | `false` by default; excludes obvious events, talent communities and similar non-vacancies using title-based rules |
| `region` | `global` by default; `eu` is available for Lever's European API region. Use `global` for Greenhouse |

When both title and location filters are provided, a listing must match **both groups**. Results are shared across the selected boards, subject to the total `maxResults` cap. Filtering is based on published text, not AI classification.

### Pricing

This Actor uses **pay-per-event** pricing: currently **$0.001 per job result** ($1 per 1,000 records), plus an Actor-start event of **$0.00005**. For example, 50 billed records correspond to $0.05005 in event charges. Only results written to the run's default dataset count as result events. Check the **Pricing** tab for current prices and use Apify's **Maximum cost per run** setting if you want a spending cap.

### Important limitations

- **Current listings only:** Each run scans the supported boards at execution time. This Actor does **not** track changes across runs, identify newly added jobs, or send alerts.
- **Supported providers:** Public Greenhouse and Lever board APIs only. Other job sites and arbitrary career-page URLs are not supported.
- **Source-dependent fields:** Some boards do not publish salary ranges, exact posting dates, workplace types, or employment types. Such fields may be blank. Conflicting source-provided workplace and location labels are not independently verified.
- **Event filtering:** Obvious non-job postings are filtered heuristically by title, so unusual event titles may occasionally remain and real vacancies may be misclassified.
- **Availability:** Public boards can change, restrict access, or remove postings. A listing URL may stop working after it was collected.
- **Large boards:** Boards with more than 1,500 published entries are currently unsupported. Individual board errors appear in the run log and `SUMMARY` record.

### Troubleshooting

**No results?** Check that `site` is the board's slug/token rather than a full URL. Remove keyword filters temporarily and confirm the public board contains vacancies. For Lever, verify whether the board uses the `global` or `eu` API region.

**Fewer results than requested?** A board may have fewer matching jobs, filters may exclude listings, some boards may fail, or the configured maximum cost per run may stop results early. `maxResults` is a ceiling, not a guaranteed count.

**One board failed?** Check the run's **Log** and the `SUMMARY` record in the default key-value store. Successful boards can still return results even when another board fails.

For questions or bug reports, use the Actor's **Issues** tab and include the board platform, site slug and relevant run details (without credentials).

# Actor input Schema

## `boards` (type: `array`):

Specify a Greenhouse token or Lever slug (not a full website URL). Maximum 10 boards per run.

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

Caps output/billable job results per run. Results are distributed across selected boards.

## `includeRecruitmentEvents` (type: `boolean`):

By default, obvious non-vacancy postings such as talent pools, networking events and interest forms are excluded.

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

If set, include titles containing any entered phrase (case-insensitive).

## `locationKeywords` (type: `array`):

If set, include locations containing any entered phrase (case-insensitive).

## Actor input object example

```json
{
  "boards": [
    {
      "platform": "lever",
      "site": "h1",
      "company": "H1",
      "region": "global"
    },
    {
      "platform": "greenhouse",
      "site": "imc",
      "company": "IMC",
      "region": "global"
    }
  ],
  "maxResults": 100,
  "includeRecruitmentEvents": false,
  "titleKeywords": [],
  "locationKeywords": []
}
```

# Actor output Schema

## `jobs` (type: `string`):

No description

## `summary` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("wheresprada/hiring-signals-pro").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("wheresprada/hiring-signals-pro").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 '{}' |
apify call wheresprada/hiring-signals-pro --silent --output-dataset

```

## MCP server setup

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

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/dTL4Klzq8kLEphOmA/builds/IgGzPCSFifFYzeFQM/openapi.json