# Breezy HR, Pinpoint & JazzHR Jobs Scraper (`bibian/multi-ats-jobs-3-scraper`) Actor

Extract job postings from company career pages hosted on Breezy HR, Pinpoint or JazzHR in one run: title, department, location, remote policy, employment type, salary and full description.

- **URL**: https://apify.com/bibian/multi-ats-jobs-3-scraper.md
- **Developed by:** [Vivien MORVAN](https://apify.com/bibian) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 1,000 job postings

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

## Breezy HR, Pinpoint & JazzHR Jobs Scraper

Extract job postings from company career pages hosted on Breezy HR, Pinpoint or JazzHR in one run: title, department, location, remote policy, employment type, salary and full description. No login, no browser.

### What you can do with it

- **Cover three ATS platforms from one Actor.** Give it company subdomains for any mix of Breezy HR, Pinpoint and JazzHR and get one combined, deduplicated dataset instead of running three separate tools.
- **Monitor specific employers.** Point it at the companies you care about and schedule a daily run to see new postings first.
- **Research salary ranges.** Breezy HR and Pinpoint often publish a salary string or range; filter the saved dataset on `salary` to see what employers disclose.
- **Feed a job board or alert.** None of these three platforms ships a public export for third parties; this Actor reads the same postings each company's own career page shows.

### Input

| Field | What it does |
|---|---|
| `breezyhrBoards` | Breezy HR company subdomains, taken from a company's career page URL, for example `seasats` from seasats.breezy.hr. |
| `pinpointBoards` | Pinpoint company subdomains, taken from a company's career page URL, for example `skims` from skims.pinpointhq.com. |
| `jazzhrBoards` | JazzHR company subdomains, taken from a company's career page URL, for example `storyteller` from storyteller.applytojob.com. |
| `maxItems` | The run stops once this many postings are saved, across all boards combined (default 150). |
| `includeDescriptions` | Add the full job description as plain text (default on). Free for Pinpoint, which already publishes it in the list; one extra request per posting for Breezy HR and JazzHR. |

Leave every board list empty for a productive default run across all three platforms.

Example input:

```json
{
  "breezyhrBoards": ["seasats"],
  "pinpointBoards": ["skims"],
  "jazzhrBoards": ["storyteller"],
  "maxItems": 150,
  "includeDescriptions": true
}
```

### Output

One record per posting:

```json
{
  "id": "pinpoint:nodalexchange:459790",
  "platform": "pinpoint",
  "company": "nodalexchange",
  "title": "Pricing Manager in Power Markets, Quantitative Risk & Strategic Analysis",
  "department": "Risk",
  "location": "Tysons Corner, Virginia",
  "remote": false,
  "employmentType": "Full Time",
  "salary": "$170,000 - $230,000 / year",
  "publishedAt": null,
  "url": "https://nodalexchange.pinpointhq.com/en/postings/3d118db6-bb21-44be-b65b-40513c590c6f",
  "description": "Pricing Manager in Power Markets..."
}
```

Export the dataset as JSON, CSV or Excel, or read it through the Apify API.

### Why this one

- **Three ATS platforms, one normalized schema.** Most competing Actors cover a single platform; this one lets a single run and a single schema span Breezy HR, Pinpoint and JazzHR together.
- **No browser, no login.** Every platform is read through a public feed or its own public career page; runs are fast and cheap.
- **Handles each platform's own quirk for a missing company.** Breezy HR and Pinpoint answer a wrong subdomain with a plain 404; JazzHR redirects it to its own marketing site instead. Both are detected and skipped with a clear warning rather than breaking the run or silently returning nothing.

### Good to know

- `salary`, when present, is the raw string or range the employer itself published; its format (currency, period) is not standardized across companies or platforms.
- `location` and `remote` are resolved from each platform's own structured fields; a posting with no place at all and a remote flag is reported as `"Remote"`.
- Each board's own `robots.txt` is checked before every run; a board whose rules disallow the relevant path is skipped with a warning rather than failing the whole run.
- Lines that carry a recruiting mailbox are removed from descriptions; no individual recruiter's name or direct contact is ever collected.
- This is an unofficial tool, not affiliated with Breezy HR, Pinpoint, JazzHR or any employer listed. Check the site terms that apply to your use.

### FAQ

**Does it work for any company, or only the ones in the default list?**
Any company whose career page is hosted on Breezy HR, Pinpoint or JazzHR. Use its subdomain in the matching input field.

**How do I find a company's subdomain?**
Open the company's own "Careers" page; if it redirects to a `*.breezy.hr`, `*.pinpointhq.com` or `*.applytojob.com` address, the part before that domain is the subdomain each field expects.

**Does it need a browser or a proxy?**
No. Every platform answers plain HTTP requests, so runs are fast and cheap.

### Try it

**[Open multi-ats-jobs-3-scraper on the Apify Store](https://apify.com/bibian/multi-ats-jobs-3-scraper)**

# Actor input Schema

## `breezyhrBoards` (type: `array`):

Breezy HR company subdomains, taken from a company's career page URL, for example "seasats" from seasats.breezy.hr. Leave every board list empty to run a default set across all three platforms.

## `pinpointBoards` (type: `array`):

Pinpoint company subdomains, taken from a company's career page URL, for example "skims" from skims.pinpointhq.com.

## `jazzhrBoards` (type: `array`):

JazzHR company subdomains, taken from a company's career page URL, for example "storyteller" from storyteller.applytojob.com.

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

The run stops once this many postings are saved, across all boards combined.

## `includeDescriptions` (type: `boolean`):

Add the full job description as plain text. Slower for Breezy HR and JazzHR (one extra request per posting); free for Pinpoint, which already publishes it in the list.

## Actor input object example

```json
{
  "maxItems": 150,
  "includeDescriptions": true
}
```

# Actor output Schema

## `postings` (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("bibian/multi-ats-jobs-3-scraper").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("bibian/multi-ats-jobs-3-scraper").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 bibian/multi-ats-jobs-3-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bibian/multi-ats-jobs-3-scraper"
        }
    }
}
```

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/5gse49cjVLtX2NkF4/builds/hMDS517hjEJatfqP6/openapi.json