# Pinpoint Jobs Scraper — Any Pinpoint Careers Page | $1/1K (`steadyrow/pinpoint-jobs`) Actor

Scrape every open job from any Pinpoint careers page: paste a company.pinpointhq.com URL or the account name. Official public postings.json feed, no proxy. Pay ranges, workplace type, employment type, filters by keyword, location, department, and a monitor mode for new jobs.

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

## Pricing

from $1.00 / 1,000 jobs

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

## Pinpoint Jobs Scraper — Any Pinpoint Careers Page | $1/1K

**Paste a Pinpoint careers page, get every open job as clean JSON. $1 per 1,000 jobs.**

Pinpoint (`<company>.pinpointhq.com`) runs the careers pages of many companies in the UK, Europe and the US. Pinpoint documents a public **`postings.json` endpoint** for showing jobs on a website. This Actor reads it and returns every posting with title, department, location, workplace type, employment type, **structured pay range** and the full description, in one request per company.

- ✅ **Any Pinpoint careers site** — `<company>.pinpointhq.com`, a posting URL, or just the account name (`impulsespace`)
- ✅ **Pay ranges** — reads Pinpoint's structured compensation when the company shows it, otherwise parses the range from the description (a range was found for 43 of 75 jobs in our test)
- ✅ **Monitor mode** — schedule it daily and only pay for jobs you have not received before
- ✅ **No browser, no proxy, no login** — one plain HTTPS request per company
- ✅ **Filters** — keywords, excluded words, location, remote, department
- ✅ **No personal data** — the hiring manager's name that Pinpoint includes in its feed is never output; e-mail addresses inside descriptions are removed

> Need Greenhouse, Lever, Ashby, Workday, Workable and more in the same run? Use the combined [ATS Jobs API](https://apify.com/steadyrow/ats-jobs). This Actor is the Pinpoint-only version with inputs built for Pinpoint.

### What can I use it for?

- **Job boards and aggregators** — pull the Pinpoint companies you track into one feed
- **Job alerts** — daily monitor run → Slack, e-mail or Google Sheets with only the new roles
- **Salary research** — published pay ranges by role, location and company
- **Hiring signals for sales and recruiting** — which departments a company is growing
- **AI agents** — a typed job feed your agent can call through the Apify API or MCP

### Input

```json
{
    "companies": [
        "https://impulsespace.pinpointhq.com",
        "intermedia",
        "pinpoint:field"
    ],
    "keywords": [
        "engineer",
        "manager"
    ],
    "excludeKeywords": [
        "intern"
    ],
    "locations": [
        "United States",
        "Remote"
    ],
    "departments": [
        "Product"
    ],
    "maxItemsPerSource": 200,
    "monitorMode": false
}
```

| Field | What it does |
|---|---|
| `companies` | **Required.** One per line: a careers site URL (`https://impulsespace.pinpointhq.com`), a posting URL (the whole site is scraped), the account name (`impulsespace` or `pinpoint:impulsespace`) or a company careers page that embeds a Pinpoint board. Entries that belong to another ATS are skipped with a note in the log. |
| `keywords` | Keep jobs whose **title** contains any of these words (whole word, case-insensitive). Turn on `searchInDescription` to search the description too. |
| `excludeKeywords` | Drop jobs whose title contains any of these words. |
| `locations` | Keep jobs whose location or country contains one of these words. `remote` matches remote jobs. |
| `departments` | Keep jobs whose department or team contains one of these strings. |
| `maxItemsPerSource` / `maxItems` | Limits per site / per run (0 = no limit). |
| `includeDescription`, `includeDescriptionHtml` | Plain-text and/or HTML description. |
| `monitorMode`, `monitorStateName` | Output only jobs not delivered before; name of the store that remembers them. |

#### Finding the account name

Open a job on the company's careers page: the address looks like `https://<account>.pinpointhq.com/en/postings/<id>`. The `<account>` part is what you need. Companies with their own domain for the careers page usually still link to their `pinpointhq.com` page; paste the company's careers page and the Actor looks for that link (some company sites block automated requests; then paste the Pinpoint URL).

### Output

One item per job:

```json
{
    "job_id": "pinpoint:intermedia:403711",
    "ats": "pinpoint",
    "company": "Intermedia",
    "company_board_id": "intermedia",
    "title": "Product Lead, Healthcare Software Solutions",
    "department": "Product",
    "team": null,
    "location": "United States",
    "locations": [
        "United States"
    ],
    "country": null,
    "remote": true,
    "workplace_type": "remote",
    "employment_type": "FULL_TIME",
    "posted_at": null,
    "updated_at": null,
    "salary_min": 155000,
    "salary_max": 186000,
    "salary_currency": "USD",
    "salary_period": "YEAR",
    "salary_source": "ats",
    "description_text": "Product Lead – Healthcare Solutions\nLocation: US, Remote…",
    "apply_url": "https://intermedia.pinpointhq.com/en/postings/3a7ab46a-6d34-42bc-84be-c8d885562d85",
    "source_url": "https://intermedia.pinpointhq.com/en/postings/3a7ab46a-6d34-42bc-84be-c8d885562d85",
    "input": "pinpoint:intermedia",
    "scraped_at": "2026-10-20T17:29:58.586Z"
}
```

Pinpoint-specific notes:

- **`posted_at` is always `null`** — Pinpoint's feed has no posting date. Consequently the `postedWithinDays` filter does not exist in this Actor's input; use monitor mode to get only new jobs.
- **The hiring manager's name is never output.** Pinpoint's feed has a `reporting_to` field with a person's name; the Actor drops it.
- `job_id` is `pinpoint:<account>:<id>` and stays the same between runs.
- `company` is derived from the account name (`impulsespace` → `Impulsespace`) because the feed does not carry a display name.
- `department` is Pinpoint's department and `team` its division (`null` when the company does not use divisions). Pinpoint has no country field (`country` is `null`).
- `salary_source` is `ats` when the company shows structured compensation, `description` when a range was parsed from the text, and all salary fields are `null` otherwise. In our main test 43 of 75 jobs had a range.
- A run summary (per site: listed / output / errors) is saved as `SUMMARY` in the default key-value store. An unknown account is reported there and in the log; the other accounts still run.

### Monitor mode: only new jobs

1. Turn on **Monitor mode** and save the input as a task.
2. Add a schedule (for example every morning).
3. The first run returns all matching jobs. Every later run returns only jobs not delivered before — and you pay only for those.

Delivered IDs are kept per site in the named key-value store `pinpoint-jobs-monitor` (change it with `monitorStateName` if you run several independent monitors). In our tests a second run on the same sites returned 0 jobs, and after forgetting 9 delivered jobs a third run returned exactly those 9.

### Pricing

Pay per event:

| Event | Price |
|---|---|
| Job in the dataset | **$0.001** ($1 per 1,000 jobs) |
| Actor start | $0.002 per run |

Examples: 1,000 jobs ≈ $1. A daily monitor on 20 sites that finds 30 new jobs ≈ $0.03 + $0.002 per day. Jobs removed by your filters or already delivered in monitor mode are not charged. Set **Maximum cost per run** and the Actor stops cleanly at the limit.

### FAQ

**How many jobs can it get?** All postings of a site, in one request. In our tests Impulse Space listed 212 open jobs, Intermedia 58 and Field 15.

**Is it legal?** The Actor reads Pinpoint's public `postings.json` endpoint, without logging in and without bypassing any protection. No recruiter or candidate data is collected, and the manager name in the feed is dropped. You are responsible for how you use the data.

**An account returns "not found".** The account name is probably wrong or the company has left Pinpoint. Open `https://<account>.pinpointhq.com` in a browser to check.

**Why is `employment_type`/`remote` empty for some jobs?** Only when the company leaves the field empty in Pinpoint.

# Actor input Schema

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

One per line. Paste a careers site URL (https://impulsespace.pinpointhq.com), a job URL (the whole site is scraped), the account name (`impulsespace` or `pinpoint:impulsespace`), or a company careers page that embeds a Pinpoint board.

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

Keep jobs whose title contains at least one of these words (whole-word, case-insensitive). Leave empty to keep all.

## `searchInDescription` (type: `boolean`):

By default keywords are matched against the job title only.

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

Drop jobs whose title contains any of these words (e.g. Senior, Intern).

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

Keep jobs whose location, any of their locations, or country contains one of these words (whole-word, case-insensitive; e.g. London, Germany, US). Use `remote` to match remote jobs.

## `remote` (type: `string`):

Filter by remote eligibility.

## `departments` (type: `array`):

Keep jobs whose Pinpoint department or division contains one of these strings (e.g. Engineering).

## `maxItemsPerSource` (type: `integer`):

Stop after this many jobs from one board. 0 = all jobs.

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

Stop the whole run after this many jobs. 0 = no limit.

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

Adds `description_text` (the full job text as plain text).

## `includeDescriptionHtml` (type: `boolean`):

Adds `description_html` (cleaned original HTML).

## `monitorMode` (type: `boolean`):

Remembers every job already delivered (per board) and outputs only jobs you have not received before. The first run outputs all matching jobs. Ideal for a daily schedule — you only pay for new jobs.

## `monitorStateName` (type: `string`):

Name of the key-value store that keeps the list of delivered jobs. Use a different name per task if you run several independent monitors.

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

Detail requests run in parallel up to this number. Requests to one ATS host are additionally limited to about 4 per second.

## Actor input object example

```json
{
  "companies": [
    "https://impulsespace.pinpointhq.com",
    "intermedia"
  ],
  "searchInDescription": false,
  "remote": "any",
  "maxItemsPerSource": 20,
  "maxItems": 0,
  "includeDescription": true,
  "includeDescriptionHtml": false,
  "monitorMode": false,
  "monitorStateName": "pinpoint-jobs-monitor",
  "maxConcurrency": 4
}
```

# Actor output Schema

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

All Pinpoint job postings collected in this run, one row per job.

# 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 = {
    "companies": [
        "https://impulsespace.pinpointhq.com",
        "intermedia"
    ],
    "maxItemsPerSource": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("steadyrow/pinpoint-jobs").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 = {
    "companies": [
        "https://impulsespace.pinpointhq.com",
        "intermedia",
    ],
    "maxItemsPerSource": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("steadyrow/pinpoint-jobs").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 '{
  "companies": [
    "https://impulsespace.pinpointhq.com",
    "intermedia"
  ],
  "maxItemsPerSource": 20
}' |
apify call steadyrow/pinpoint-jobs --silent --output-dataset

```

## MCP server setup

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

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/65KVgDLc6mO8Gehso/builds/WjnK6LCHBQag5E1wF/openapi.json