# Company Hiring Signal (`toronto_777/company-hiring-signal`) Actor

Turn company names or career URLs into hiring signals: job counts, U.S. and regional roles, remote roles, sample jobs, and evidence URLs.

- **URL**: https://apify.com/toronto\_777/company-hiring-signal.md
- **Developed by:** [Steven Feng](https://apify.com/toronto_777) (community)
- **Categories:** Developer tools, Lead generation, Automation
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-usage

## 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

## Company Hiring Signal

Company Hiring Signal summarizes public hiring activity from company career pages and supported ATS job boards. It is intended for market research, lead qualification, and lightweight hiring-demand monitoring.

### What It Does

- Accepts company domains or public career URLs.
- Detects supported ATS boards where possible.
- Normalizes visible job postings from public sources.
- Produces hiring signal counts, sampled jobs, evidence URLs, and fetch status.
- Falls back to discovering career links on generic pages when job counts cannot be extracted.

### Input Fields

- `companies`: required list of company domains or public career URLs.
- `regionHints`: retained for input compatibility; MVP location classification uses shared location rules.
- `maxJobsPerCompany`: maximum normalized jobs included in each output record.
- `includeJobSamples`: when false, output records keep counts and scores but return an empty `jobs` sample list.
- `detectAts`: when true, detects Greenhouse, Lever, Ashby, and generic career pages from the URL.

### Output Fields

Each dataset item contains:

- `status`: `ok`, `partial`, or `failed`.
- `errors`: non-fatal limitations or per-company fetch failures.
- `evidence`: URLs used for the record.
- `ats`: detected ATS type.
- `summary`: total, US, remote, hybrid, and signal score counts.
- `jobs`: normalized sampled jobs.
- `careerLinks`: generic career links discovered on fallback pages. These are not counted as jobs.

### Limits And Safety Boundaries

Greenhouse and Lever use public JSON endpoints. Ashby is detected but returned as `partial` with `UNSUPPORTED_ATS_FETCH` until a stable low-maintenance fetch path is added.
Generic pages are limited to career-link extraction from the supplied page and may return `careerLinks` with zero counted jobs, plus `GENERIC_PAGE_ONLY` or `NO_JOBS_FOUND`.

This Actor uses public pages and public ATS endpoints only. It does not scrape LinkedIn, log in, bypass CAPTCHA, apply to jobs, collect private personal data, or enrich people profiles.

# Actor input Schema

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

Company domains or public career URLs.

## `regionHints` (type: `array`):

Optional region labels used by clients to document the hiring regions they care about.

## `maxJobsPerCompany` (type: `integer`):

Maximum number of normalized job samples to include for each company.

## `includeJobSamples` (type: `boolean`):

Whether to include individual sampled jobs in addition to aggregate hiring metrics.

## `detectAts` (type: `boolean`):

Whether to detect supported applicant tracking systems from each input URL.

## Actor input object example

```json
{
  "regionHints": [
    "US",
    "Remote"
  ],
  "maxJobsPerCompany": 100,
  "includeJobSamples": true,
  "detectAts": true
}
```

# Actor output Schema

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

Dataset items with one record per company, including job counts, region matches, remote counts, sample jobs, warnings, and evidence URLs.

## `summary` (type: `string`):

Key-value store OUTPUT record containing totalRecords and the records returned by this run.

# 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("toronto_777/company-hiring-signal").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("toronto_777/company-hiring-signal").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).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 toronto_777/company-hiring-signal --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=toronto_777/company-hiring-signal",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/fjdy8wXzDld1AOQ7W/builds/CLYkM5hODAoIKMoqH/openapi.json