Workable API
Workable publishes a public REST API (currently v3) at workable.readme.io plus a developer and partner program. Auth is an API token a Super Admin generates under Integrations. Endpoints cover jobs, candidates, pipeline stages, members, events, and a careers-page feed.
Frequently asked questions
Workable scores A on the API Report Card. Workable publishes a public REST API (currently v3) at workable.readme.io plus a developer and partner program. Auth is an API token a Super Admin generates under Integrations. Endpoints cover jobs, candidates, pipeline stages, members, events, and a careers-page feed.
Workable has a workable official integration path. Most engineering teams can build against it directly. Open API: self-serve, documented, with SDKs
Workable is an all-in-one recruiting and HR platform that combines applicant tracking (ATS), talent sourcing, employee management, time tracking, and payroll.
Industry-agnostic HR/recruiting software targeting SMBs through mid-market employers, with growing enterprise reach. 30,000+ customers across 100+ countries, including Ryanair, Sephora, the LA Clippers, and Bulb. Recruiters and hiring managers use Workable to post jobs to aggregators, source passive candidates, screen resumes with AI, schedule interviews, collect structured feedback, send offers, and onboard new hires.
High within the SMB/mid-market ATS segment. 30,000+ paying customers makes it one of the larger independent ATS vendors (behind Greenhouse and Lever in enterprise mindshare but ahead of many newer entrants).
Founded: 2012 (Athens, Greece). HQ: Boston, MA (offices in London, Athens, Singapore). Founders: Nikos Moraitakis, Spyros Magiatis. Employees: 251–500. Funding: ~$84M raised (investors include 83North, Balderton Capital, Openfund, Zouk Capital).
Founded 2012, ~13 years old. Modern SaaS architecture, actively shipping AI features (AI Recruiter, candidate scoring, JD generation).
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.