# Company Hiring Signals (Greenhouse, Lever, Ashby, Recruitee) (`velveteen_driver/hiring-signals`) Actor

Give it company websites and get their open jobs from the public Greenhouse, Lever, Ashby and Recruitee job feeds, with flags for companies hiring in sales, marketing or engineering. A buying-signal feed for sales and recruitment teams.

- **URL**: https://apify.com/velveteen_driver/hiring-signals.md
- **Developed by:** [Elliott](https://apify.com/velveteen_driver) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$5.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?

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

## Company Hiring Signals (Greenhouse, Lever, Ashby, Recruitee)

A company that's hiring is growing, has budget and is changing how it works: the best time to reach it. Give this actor a list of company websites and get back, for each one:

- **Which job board** it uses: Greenhouse, Lever, Ashby or Recruitee (the only boards supported)
- **How many roles** are open, and the **newest posting date**
- **Hiring flags**: sales, marketing, engineering, product/design, customer, operations/finance, people/HR, leadership
- **Every role**: title, department (not available from Greenhouse boards), location, link and posting date
- **Top hiring locations**

### Ideas

- **Sales teams**: sell recruitment, onboarding, HR, or tools for the team that's growing ("hiring 5 SDRs" = buying sales tools).
- **Agencies**: companies hiring their first marketer often need outside help in the meantime.
- **Recruiters**: track open roles across your target accounts every week.
- **Investors**: watch headcount growth across a portfolio or market.

Tick **Only return companies with open roles** to get a clean list of hiring companies. You're only charged for rows returned.

### How it finds the jobs

It reads the website you give and looks for a link to the company's job board. If there isn't one on that page, it opens up to 3 careers pages linked from it, but only where that site's robots.txt allows it. It then reads the board's **public job feed**, the same feed the company's own careers page uses. EU-hosted Lever boards are read from Lever's EU feed (`api.eu.lever.co`). EU-hosted Greenhouse boards (`job-boards.eu.greenhouse.io/<board>`) are served by the same Greenhouse Job Board API as every other Greenhouse board (`boards-api.greenhouse.io`); `atsRegion` shows `eu` when the link pointed to an EU board.

When the website hides the link, it can try the board named after the domain (e.g. `stripe.com` → Greenhouse board `stripe`). Those rows say so in `matchedBy` ("board named after the domain"), because a board with that name could belong to a different company: check them before relying on them.

### Output fields

`website`, `ats`, `atsBoard`, `atsRegion`, `openRoles`, `hiringFunctions`, `hiringSales`, `hiringMarketing`, `hiringEngineering`, `newestPostingAt`, `locations`, `roles` (each with `title`, `department` (null for Greenhouse, where hiring flags come from the job title), `location`, `url`, `postedAt`, and for Greenhouse also `updatedAt`), `careersPage`, `matchedBy`, `error`.

`postedAt` is the date the job was first published (Greenhouse `first_published`, Lever `createdAt`, Ashby `publishedAt`, Recruitee `published_at`), as the board gives it. `newestPostingAt` is the latest of these, compared as real dates across time zones and returned in ISO 8601 UTC (for example `2026-10-01T14:00:00Z`).

### Data source and licence

Rows come only from public job feeds that each job board provides for public, automated use, plus the company websites you supply:

- Greenhouse Job Board API: https://developers.greenhouse.io/job-board.html (`boards-api.greenhouse.io`, which also serves EU-hosted boards)
- Lever Postings API: https://github.com/lever/postings-api (`api.lever.co`, `api.eu.lever.co`)
- Ashby public Job Posting API: https://developers.ashbyhq.com/docs/public-job-posting-api (`api.ashbyhq.com`)
- Recruitee Careers Site API: https://docs.recruitee.com/reference/intro-to-careers-site-api (`<company>.recruitee.com/api/offers/`)

The job listings belong to the companies that published them. The actor returns facts about open roles (title, team, location, link, date), not full job descriptions.

### Responsible use

- The actor identifies itself honestly with the User-Agent `Mozilla/5.0 (compatible; HiringSignalsBot/1.0; +https://apify.com/velveteen_driver/hiring-signals)`.
- It follows robots.txt for every page and feed beyond the website you give (including `Crawl-delay`, so `api.lever.co` gets at most 1 request a second), waits at least 1 second between requests to the same host, and backs off when a server says it's busy.
- It never logs in, never reads LinkedIn, Indeed, Glassdoor or other sites whose terms forbid automated access, and collects no personal data.
- Use the results lawfully, for example under UK GDPR and PECR when you contact businesses, and within Apify's terms.

# Actor input Schema

## `websites` (type: `array`):

One per line, e.g. stripe.com

## `onlyHiring` (type: `boolean`):

You're only charged for the companies returned.

## `guessBoardFromDomain` (type: `boolean`):

When the website doesn't link to its job board, try the Greenhouse, Ashby and Lever boards named after the domain. Marked in 'matchedBy' so you can check it's the same company.

## `maxRolesPerCompany` (type: `integer`):

How many individual job listings to include per company (counts and flags always cover all roles).

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

How many companies to check in parallel. Requests to any one host (including each job board API) are always spaced at least 1 second apart.

## Actor input object example

```json
{
  "websites": [
    "notion.so",
    "gocardless.com"
  ],
  "onlyHiring": false,
  "guessBoardFromDomain": true,
  "maxRolesPerCompany": 200,
  "maxConcurrency": 10
}
```

# Actor output Schema

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

All results in the default dataset, shown in the overview table.

# 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 = {
    "websites": [
        "notion.so",
        "gocardless.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("velveteen_driver/hiring-signals").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 = { "websites": [
        "notion.so",
        "gocardless.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("velveteen_driver/hiring-signals").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 '{
  "websites": [
    "notion.so",
    "gocardless.com"
  ]
}' |
apify call velveteen_driver/hiring-signals --silent --output-dataset

```

## MCP server setup

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

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/O7m6qOGpopMywQ7Cy/builds/fvBcvUYhwXaOAJhtr/openapi.json