Scrape Workable Job Postings Without Managing Proxies or Browsers
Workable hosts public career pages for many employers.
If you need to watch open roles, compare postings across companies, or study hiring pace, this API takes a Workable URL and is designed to return the page after JavaScript rendering and proxy rotation. You can keep the rendered HTML or ask for structured fields such as title, employer, location, posting date, required skills, description, salary range, and application URL.
What you can do with Workable job-board data
Start by deciding whether you need a point-in-time snapshot or a longitudinal series. A snapshot answers "what is open right now" for a set of employers and is enough for headcount benchmarking or a one-off skills audit. A longitudinal series answers "how is this changing" and requires you to store each posting's first-seen and last-seen dates so you can distinguish a genuinely new role from one that was reposted after closing. For pay or skills research, capture the full posting text rather than only the title, because salary ranges and required skills usually live in the body. Each of these starts from a public Workable URL and a single API call.
Fields returned per posting
When you request structured output, a Workable job page can yield: job title, employer, location, posting date, required skills, full description, salary range, and application URL. If you prefer to parse yourself, the API can return rendered HTML instead. The choice matters for downstream work: structured JSON saves selector maintenance, while raw HTML keeps every element available for custom parsing.
Choose request options deliberately
Start with the simplest request and add options only when the page needs them. Use render_js when content depends on JavaScript. Use stealth_proxy when a page presents CAPTCHA-style challenges. Use country_code when the content you need varies by geography. Use extract_rules with CSS selectors, or ai_extract_rules with a natural-language description, when you want parsed JSON rather than HTML. Each option changes credit cost, so estimate before running a large batch.
Credit-cost example
The figures below are illustrative only; substitute the rates your account confirms. Suppose a JavaScript-rendered request costs {{OWNER_CREDIT_RATES_JS}} credits and a premium-proxy request with JS costs {{OWNER_CREDIT_RATES_PREMIUM_JS}} credits. For 1,000 pages at the premium-proxy-with-JS rate, multiply 1,000 by {{OWNER_CREDIT_RATES_PREMIUM_JS}} to get the batch total. If you add stealth_proxy at {{OWNER_CREDIT_RATES_STEALTH}} credits per request, multiply 1,000 by that figure instead. Confirm current rates on the pricing page before committing a budget.
Concurrency versus target throttling
The API enforces concurrency limits by plan, not a fixed per-target request rate. If Workable or an employer page starts throttling aggressive patterns, spread requests over time or use multiple sessions. That is a target-side behavior, separate from your plan's concurrent-request ceiling.
Setup path
Create an account to get an API key and any free test credits your plan includes ({{OWNER_FREE_CREDITS}}). Install an SDK for Python, Node.js, Go, PHP, Ruby, or Java, or send a plain cURL request. Pass a Workable URL on workable.com. The service is designed to render JavaScript, rotate residential proxies, and return the page. Code samples and a dashboard request builder are available if you want to test before writing pipeline code. These capability statements describe the intended request contract; they are not a claim that a specific run was executed or verified against a live Workable page.
Related capabilities
Beyond HTML and JSON, the same platform offers full-page screenshots for visual records of listings before they close, Markdown output for LLM workflows, JavaScript scenarios for clicking or scrolling before capture, and Google Search results for tracking where Workable jobs are discovered. An n8n integration supports job-monitoring automation without scraper code.
Frequently asked questions
Do I need a Workable account to scrape public job pages?
No external Workable account is required. You sign up for an API key, send the public Workable URL, and the service handles rendering and proxies. Free starting credits are {{OWNER_FREE_CREDITS}}.
Can requests appear to come from a specific country?
Yes. Pass country_code on the request to route through a residential IP in that country. This helps when job content or availability differs by geography.
Is there a per-target rate limit for Workable?
The API applies concurrency limits by plan rather than a fixed per-target rate. If a target throttles aggressive request patterns, space out requests or use multiple sessions.
How do I get structured JSON instead of HTML?
Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language specification. The response is parsed JSON.
Which languages and tools can I use?
SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java. Plain cURL also works. Choose whatever your existing stack uses.
How are credits charged for Workable scraping?
New accounts receive {{OWNER_FREE_CREDITS}}. Paid plans start at {{OWNER_PLAN_PRICES}} for higher volume and concurrency. Per-request credit cost depends on options: {{OWNER_CREDIT_RATES_JS}} credits for JavaScript rendering, {{OWNER_CREDIT_RATES_PREMIUM_JS}} for premium_proxy with JS, and {{OWNER_CREDIT_RATES_STEALTH}} for stealth_proxy. Check the current pricing page for up-to-date plan details.