[NewSearch millions of jobs from your AI agent with MCP→](/blog/jobspipe-mcp-server)

[All posts](/blog)

Guide·Jul 16, 2026·5 min read

# Workable API: pulling published job postings across every account

Workable advertises a public Job Board API, but even that is gated per account - each customer must grant you their own credentials. Where the Workable API surfaces run out, and how to pull every account's postings through one normalized jobs API.

![Dvir Atias](/authors/dvir-atias.jpg)

Dvir Atias

Founder, JobsPipe

Workable is a widely used ATS, and unlike most it advertises a public Job Board API - which is why **Workable API** looks like an easy win for job data. The catch shows up fast: even the “public” surface is gated per account.

## The Workable API surfaces

-   **The Job Board API** - read-only published postings for a single account. It reads public, but Workable requires each customer to grant you their own credentials, so it is not open across the Workable universe.
-   **The main Workable API** - the OAuth-scoped REST surface for customers and partners: jobs, candidates, and the full hiring pipeline, plus webhooks. Scoped to one account.

## Public, but one account at a time

Every Workable surface is keyed to a single customer’s account. There is no directory of Workable employers, no cross-account search, and no aggregator-tier credential. To cover many employers you first need each one’s access - the discovery-and-permission work that per-account APIs always push onto you.

## Every Workable account through one jobs API

JobsPipe indexes public Workable postings and returns them through one normalized [jobs API](/jobs-api), with parsed salary and resolved locations, alongside 30+ other sources:

```
curl https://api.jobspipe.dev/v1/jobs/search \
  -H "Authorization: Bearer jp_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{ "source_or": ["workable"], "job_title_or": ["customer success"], "remote": true }'
```

No per-account onboarding. Narrow to one employer with `company_name_partial_match_or`. Field-level docs on our [Workable jobs API guide](/guides/workable-jobs-api) and [Workable source page](/sources/workable); see how it stacks up in [the best jobs APIs of 2026](/blog/best-jobs-api-2026).

Every Workable account, one jobs API - 30+ sources, free tier included.

## Frequently asked questions

### Is the Workable API free?

Workable's Job Board API can return an account's published postings, but even that surface is gated per account - each customer must grant you their own credentials. There is no free, cross-account Workable jobs feed.

### How do I get job postings from every Workable account?

Workable has no directory or cross-account search. JobsPipe indexes public Workable postings and serves them through one normalized jobs API, alongside 30+ other sources, so you skip per-account onboarding.

[

← Previous

BambooHR API: the HRIS API vs the job postings you actually want

](/blog/bamboohr-api-jobs)[

Next →

Teamtailor API: clean JSON:API, one key per tenant - and the fix

](/blog/teamtailor-api-jobs)

---
Canonical URL: https://jobspipe.dev/blog/workable-api-jobs
Title: Workable API: pulling published job postings across every account
Description: Workable advertises a public Job Board API, but even that is gated per account - each customer must grant you their own credentials. Where the Workable API surfaces run out, and how to pull every account's postings through one normalized jobs API.