Source · PinpointPinpoint Jobs API.
Every public Pinpoint career site, one endpoint. Same schema as Workday, Indeed, and 30+ other sources.
Why people are confused about the Pinpoint API
Pinpoint exposes an Embed API and a Webhooks API to its existing customers, both scoped per-customer with account-level credentials. There is no public cross-customer endpoint that lists jobs across the Pinpoint universe.
Pinpoint customers host their careers pages at <company>.pinpointhq.com (and on customer-owned domains via Pinpoint embeds). JobsPipe indexes every public Pinpoint careers page and normalizes the data into the same schema as our other sources.
Each Pinpoint customer must individually issue API access. Workable for a single named partner; not practical for cross-customer coverage.
Possible but each customer is its own scraper config and the markup occasionally shifts between Pinpoint releases.
Every public Pinpoint customer, one endpoint, same JSON schema as the rest of JobsPipe.
Pinpoint API documentation
Pinpoint developer documentation lives at developers.pinpointhq.com. The main surfaces are the Embed API (for customers embedding jobs on their own marketing site), the Webhooks API (for customer-side event handling), and the Reporting API (gated). Like most ATSs, Pinpoint has no public cross-customer endpoint - keys are scoped to a single account. JobsPipe's documentation at /docs covers the unified schema we return for every public Pinpoint careers page, alongside 30+ other ATSs in the same shape.
Pinpoint API key
Pinpoint API keys are minted inside the customer's Pinpoint admin under Integrations > API Access. Each key is account-scoped, with separate keys per integration surface. JobsPipe doesn't require Pinpoint credentials - we consume only public Pinpoint careers pages and authenticate with one JobsPipe key.
Pinpoint API integration
Single-customer Pinpoint integration goes through that customer's API key flow. Cross-customer aggregator integration is JobsPipe - every public Pinpoint customer, one endpoint, normalized into the same JSON schema as 30+ other ATSs.
Sample request
curl "https://api.jobspipe.dev/v1/jobs?source=pinpoint" \
-H "Authorization: Bearer $JOBSPIPE_KEY" \
-H "Accept: application/json"Sample response
{
"id": "pp_dXJ5MGlxc2RmcWVm",
"source": "pinpoint",
"tenant": "lendable",
"title": "Senior Platform Engineer",
"company": "Lendable",
"location": {
"city": "London",
"region": null,
"country": "GB",
"remote": false
},
"salary": {
"min": 95000,
"max": 130000,
"currency": "GBP",
"period": "year",
"source": "explicit"
},
"employment_type": "full_time",
"posted_at": "2026-05-11T11:42:00Z",
"expires_at": null,
"apply_url": "https://lendable.pinpointhq.com/postings/...",
"description": "Lendable is hiring a Senior Platform Engineer for our credit-decisioning infrastructure ..."
}Every Pinpoint job record is returned in the same JSON shape as every other JobsPipe source. The full schema is documented in the docs.
Fields in every Pinpoint job record
FAQ
Does JobsPipe need a Pinpoint Embed API key per customer?+
No. JobsPipe pulls only public-facing Pinpoint careers data - what any anonymous visitor can see. We never have access to private Embed API endpoints or candidate data.
How fresh is Pinpoint data?+
Pinpoint careers pages are re-crawled at least every 24 hours.
Can I filter to one Pinpoint customer?+
Yes. ?tenant=lendable filters to jobs from that one company's Pinpoint page.
Are Pinpoint jobs deduped against other sources?+
Yes. When the same posting appears on Pinpoint and on Indeed/Glassdoor/etc, JobsPipe links them as one canonical job record.
Try Pinpoint data free - 5,000 requests/month, no credit card.
Get a free API key