Workable Python API Docs | dltHub
Build a Workable-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Workable API is a platform that allows access to account jobs, candidates, offers, stages, departments, and members. The REST API base URL is https://{subdomain}.workable.com/spi/v3 and All requests require a Bearer token for authentication..
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Workable data in under 10 minutes.
What data can I load from Workable?
Here are some of the endpoints you can load from Workable:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| jobs | /jobs | GET | Returns a collection of your account jobs. | |
| candidates | /candidates | GET | candidates | Returns a list of candidates. |
| candidate | /candidates/:id | GET | Returns a specific candidate object. | |
| offers | /offers/:id | GET | Returns a specific offer object. | |
| stages | /stages | GET | stages | Returns a list of stages. |
| departments | /departments | GET | departments | Returns a list of departments. |
| members | /members | GET | members | Returns a list of members. |
| job_questions | /jobs/:shortcode/questions | GET | questions | Returns a list of associated application questions for a job. |
How do I authenticate with the Workable API?
Authentication requires a Bearer token passed in the Authorization header (Authorization: Bearer <ACCESS_TOKEN>).
1. Get your credentials
- Log in to your Workable account.
- Navigate to 'Integrations'.
- Locate and select 'Generate API token'.
- Follow the on-screen instructions to generate a new API token. Note that the token will only be displayed once.
2. Add them to .dlt/secrets.toml
[sources.workable_source] token = "your_api_token_here"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
dlt ai toolkit rest-api-pipeline install
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Workable API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
python workable_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline workable_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset workable_data The duckdb destination used duckdb:/workable.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline workable_pipeline show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads jobs and candidates from the Workable API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def workable_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{subdomain}.workable.com/spi/v3", "auth": { "type": "bearer", "token": token, }, }, "resources": [ {"name": "jobs", "endpoint": {"path": "jobs"}}, {"name": "candidates", "endpoint": {"path": "candidates", "data_selector": "candidates"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="workable_pipeline", destination="duckdb", dataset_name="workable_data", ) load_info = pipeline.run(workable_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("workable_pipeline").dataset() sessions_df = data.jobs.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM workable_data.jobs LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("workable_pipeline").dataset() data.jobs.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Workable data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Troubleshooting
Rate Limits
Workable API has a rate limit of 10 requests per 10 seconds. Exceeding this limit will result in an HTTP 429 error.
Pagination
Many list endpoints support pagination. Endpoints like /jobs return collections directly. For other resources, the list of records is typically found under a key matching the resource name (e.g., candidates for /candidates, departments for /departments, stages for /stages, members for /members). For job-specific sub-resources, the list keys are per the endpoint name (e.g., questions for /jobs/:shortcode/questions).
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Workable?
Request dlt skills, commands, AGENT.md files, and AI-native context.