# Pinpoint Jobs API - Career Page Scraper & Pay Ranges (`starbright_overlap/pinpoint-jobs-scraper`) Actor

Pinpoint jobs API and career page scraper. Read live postings from any Pinpoint job board or careers page, or search hundreds of known Pinpoint ATS boards in one run. Full descriptions, and a structured pay range on 42.5% of postings.

- **URL**: https://apify.com/starbright\_overlap/pinpoint-jobs-scraper.md
- **Developed by:** [Sulle H](https://apify.com/starbright_overlap) (community)
- **Categories:** Jobs, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

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

## Pinpoint Jobs Scraper — 620 Career Sites, Full Descriptions

Pinpoint is a UK-rooted applicant tracking system used by mid-market and scale-up employers. Its
public endpoint is unusually generous: **every posting comes with structured description content**,
not just a title and a link.

Point it at a company, or leave the list empty and search a bundled registry of **620 live
Pinpoint career sites** carrying **18,241 open postings**.

```json
{ "keywords": ["analyst"], "maxJobs": 200 }
```

```json
{ "companies": ["https://10kai.pinpointhq.com"] }
```

No login, no cookies, no proxies, no API key.

### The description is split into real sections

Most ATS platforms hand you one blob of HTML. Pinpoint separates the posting into fields the
employer filled in deliberately:

- the role summary
- **key responsibilities**
- **skills, knowledge and expertise**
- benefits

This Actor joins them into `descriptionText` as readable plain text, in that order, so the structure
survives as paragraphs rather than being lost in markup. Measured across live boards, description
content is present on **100%** of rows.

### What you get

| Field | Description |
|---|---|
| `provider` | Always `pinpoint` — the same schema the multi-ATS Actors below emit |
| `company` / `companySlug` | Employer subdomain |
| `jobId` | Pinpoint posting id — stable, so it works as a dedupe key across runs |
| `title` | Job title |
| `location` | Office location, e.g. `London` |
| `department` | Department, from the employer's own org structure |
| `employmentType` | Full-time, contract, internship, as the employer classified it |
| `remote` | Derived from Pinpoint's `workplace_type` (onsite / hybrid / remote) |
| `applyUrl` | Direct link to the posting |
| `descriptionText` | Summary, responsibilities and required skills, as plain text |
| `salary` | Present only when the employer filled it in — see below |
| `scrapedAt` | When this row was read |

### Pay ranges, on more than a third of postings

Pinpoint asks employers for a minimum, a maximum, a currency and a period, and stores them as
separate numbers rather than a sentence. Measured across **every live board in this registry —
17,302 postings from 615 boards — 42.5% carry a pay range.**

```json
{ "salary": "45000–55000 GBP annual" }
```

Four platforms in this family publish pay, and they differ in form and in how often it is filled:

| Platform | Pay present | Form |
|---|---|---|
| Breezy HR | 45.7% | Free text, as the employer wrote it |
| **Pinpoint** | **42.5%** | **Separate numbers — min, max, currency, period** |
| Ashby | 38.9% | Prose summary, sometimes with an equity note |
| Recruitee | 26.9% | Separate numbers, mostly European currencies |

Pinpoint and Recruitee are the two that give you numbers you can compare, which is what you want
for benchmarking. The remaining platforms expose no salary field whatsoever, and no scraper can
invent one.

The remaining 57.5% come back `null` because the employer left the fields blank — not because the
Actor failed to read them.

**There is no posting date, though.** Pinpoint exposes a `deadline_at` rather than a published date,
so `postedAt` is `null` and `postedWithinDays` keeps these rows rather than dropping them.

### Input

| Option | What it does |
|---|---|
| `keywords` | Keep only titles containing one of these. Case-insensitive. |
| `excludeKeywords` | Drop titles containing any of these, e.g. `senior`, `intern`. |
| `locations` | Keep only locations containing one of these. |
| `remoteOnly` | Keep only postings Pinpoint marks as remote. |
| `postedWithinDays` | Freshness filter. Pinpoint rows have no date and are always kept. |
| `companies` | Subdomains or board URLs. Leave empty to search all 620. |
| `maxBoards` | How many boards to scan, largest-first. |
| `maxJobs` | Hard cap on rows, so a run costs what you expect. |

### Finding a company slug

The board lives at `<slug>.pinpointhq.com`, so the slug is the subdomain. Paste the whole URL and
the Actor extracts it. Or run without `companies` and read the `companySlug` column.

### Recipes

**Full-text search across employers.** Responsibilities and required skills come back as plain text,
so one run gives you a corpus you can grep for a tool, a certification or a seniority signal that
the title never mentions.

**Watch one company.** One slug, run on a schedule, diff `jobId` between runs.

**Feed a niche job board.** Every row carries the employer's own `applyUrl`, so your users apply at
the source rather than through a middleman.

### Pricing

Pay per result — you are charged per job row delivered. A board that fails or returns nothing costs
you nothing. Platform usage is included rather than billed on top.

### Beyond Pinpoint

Companies move between applicant tracking systems, and most job-data projects need more than one:

- **[Career Site Job Feed](https://apify.com/starbright_overlap/ats-job-feed)** — the same engine
  across every platform in this family, in one run, with an identical output schema.
- **[New Job Alerts](https://apify.com/starbright_overlap/new-jobs-feed)** — the same coverage, but
  each run returns only what appeared since the previous run.

### Notes

- **A dead slug never aborts the run.** Failures land in a `FAILED_BOARDS` record in the key-value
  store, with the reason for each.
- **`companySlug:jobId` is a stable key**, safe for detecting what opened and closed between runs.
- **No login, no proxies, no API key.** Pinpoint publishes this endpoint openly. Private boards are
  invisible to every scraper, including this one.

# Actor input Schema

## `keywords` (type: `array`):

Keep only jobs whose title contains at least one of these. Case-insensitive. Leave empty for every job.

## `excludeKeywords` (type: `array`):

Drop jobs whose title contains any of these, e.g. `senior`, `intern`.

## `locations` (type: `array`):

Keep only jobs whose location contains one of these, e.g. `london`, `new york`, `germany`.

## `remoteOnly` (type: `boolean`):

Keep only postings flagged remote by the ATS or with a remote-looking location.

## `postedWithinDays` (type: `integer`):

Freshness filter. Defaults to 90 days because some employers leave postings open for years — measured across the registry, 15% of Greenhouse and about half of the largest SmartRecruiters boards are over a year old. Set a large number such as 3650 to include everything. Postings with no publication date (most Workday rows) are always kept.

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

Board slugs, e.g. `trilongroup`. Leave empty to search all 620 known pinpoint employers.

## `maxBoards` (type: `integer`):

Boards are scanned largest-first, so a capped run still returns the most jobs. Raise it to sweep all 620 boards.

## `maxJobs` (type: `integer`):

Hard cap on results, so a run costs what you expect. Defaults to 500 — enough to evaluate the feed on free-tier credits. Clearing the box falls back to that, so type a large number such as 500000 to sweep everything.

## `includeDescription` (type: `boolean`):

Fetch the full description text. Available on Greenhouse, Workable, Ashby and Breezy. SmartRecruiters and Workday do not expose descriptions on their listing endpoints, so those rows return null however this is set. Turning it off makes runs several times faster.

## `concurrency` (type: `integer`):

Higher is faster but more likely to hit ATS rate limits.

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

Keeps one huge employer from filling the whole run. Boards are scanned largest-first, so without this the first few boards use up the entire result budget. Raise it when you want depth on a few employers rather than breadth across many.

## Actor input object example

```json
{
  "keywords": [
    "engineer"
  ],
  "remoteOnly": false,
  "postedWithinDays": 90,
  "maxBoards": 300,
  "maxJobs": 500,
  "includeDescription": true,
  "concurrency": 8,
  "maxJobsPerCompany": 25
}
```

# Actor output Schema

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

Every posting matching your filters, normalized across all six ATS platforms.

## `failedBoards` (type: `string`):

Written only when a board was unreachable or rate-limited. The run itself is unaffected.

# 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 = {
    "keywords": [
        "engineer"
    ],
    "postedWithinDays": 90,
    "maxJobs": 500,
    "maxJobsPerCompany": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("starbright_overlap/pinpoint-jobs-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 = {
    "keywords": ["engineer"],
    "postedWithinDays": 90,
    "maxJobs": 500,
    "maxJobsPerCompany": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("starbright_overlap/pinpoint-jobs-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 '{
  "keywords": [
    "engineer"
  ],
  "postedWithinDays": 90,
  "maxJobs": 500,
  "maxJobsPerCompany": 25
}' |
apify call starbright_overlap/pinpoint-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,starbright_overlap/pinpoint-jobs-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/41Ka5ydujBJn8aBbG/builds/rrCmwXmiUKPNkjTWB/openapi.json