Workable (via Apideck)

Access Workable through Apideck's ATS unified API — one of 11 ATS connectors that share the same method surface. Code you write here ports to Greenhouse, Workday, Lever and 7 other ATS connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Workable plumbing.

Beta connector. Workable is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.

Quick facts

Apideck serviceId: workable
Unified API: ATS
Auth type: oauth2
Status: beta
Gotchas: page
Workable docs: https://workable.readme.io
Homepage: https://workable.com

At a glance

Implementation difficulty: straightforward — Self-Service OAuth via Apideck's Approved Workable App, No Partnership of Your Own
Vendor partnership required: no
Apideck-managed credentials: available — OAuth shows "Apideck" as the requesting application.
Account type required: Workable account, identified by its account subdomain.
Consumer access level: Workable does not state a minimum role for the authorisation. The connection then reaches only the jobs and candidates the authorising user can access.
Sandbox: available (signup) — 15-day free Workable trial, no card required; Workable does not say whether trial accounts can use the API.
Costs: Workable publishes no API fee and does not say which plans include API access.
Rate limits: 50 requests per 10 seconds.
Authentication: Authorization Code flow.
Webhooks: Virtual webhooks - applicant and job created and updated events.

Facts synced from Apideck's connector metadata API — GET /connector/connectors/workable (overview field) is the live, authoritative version.

When to use this skill

Activate this skill when the user explicitly wants to work with Workable — for example, "list open jobs in Workable" or "move an applicant through stages in Workable". This skill teaches the agent:

Which Apideck unified API covers Workable (ATS)
The correct serviceId to pass on every call (workable)
Workable-specific auth and coverage caveats

For the full method surface (parameters, pagination, filtering), use your language SDK skill:

apideck-node, apideck-python, apideck-dotnet, apideck-java, apideck-go, apideck-php, or apideck-rest

For the raw OpenAPI spec:

ATS: https://specs.apideck.com/ats.yml · API Explorer

Minimal example (TypeScript)

import { Apideck } from "@apideck/unify";

const apideck = new Apideck({
  apiKey: process.env.APIDECK_API_KEY,
  appId: process.env.APIDECK_APP_ID,
  consumerId: "your-consumer-id",
});

// List applicants in Workable
const { data } = await apideck.ats.applicants.list({
  serviceId: "workable",
});

Portable across 11 ATS connectors

The Apideck ATS unified API exposes the same methods for every connector in its catalog. Switching from Workable to another ATS connector is a one-string change — no rewrite, no new SDK.

// Today — Workable
await apideck.ats.applicants.list({ serviceId: "workable" });

// Tomorrow — same code, different connector
await apideck.ats.applicants.list({ serviceId: "greenhouse" });
await apideck.ats.applicants.list({ serviceId: "workday" });

This is the compounding advantage of using Apideck over integrating Workable directly: code against the unified ATS API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.