Workiz Python API Docs | dltHub

Workiz is a field-service management platform offering scheduling, invoicing, CRM, and job management via a REST API. The REST API base URL is https://api.workiz.com/api/v1/ and API uses a token pair (API token and API secret) 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 Workiz data in under 10 minutes.

---

What data can I load from Workiz?

Here are some of the endpoints you can load from Workiz:

---

How do I authenticate with the Workiz API?

Enable the Developer API add‑on in Workiz, then obtain an API token and API secret from Settings > Integrations > Developer. The token is used in the request URL (e.g., https://api.workiz.com/api/v1/{api_token}/...), while the secret is required for signed requests but its exact placement is not documented.

1. Get your credentials

1. In Workiz app, open Feature Center and enable Developer API. 2) Click the profile icon > Settings. 3) Under Integrations select Developer. 4) Copy the API token and API secret shown.

2. Add them to .dlt/secrets.toml

Copy
[sources.workiz_source]
api_token = "your_api_token_here"
api_secret = "your_api_secret_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:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
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:

Copy
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 Workiz 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:

Copy
python workiz_pipeline.py

If everything is configured correctly, you'll see output like this:

Copy
Pipeline workiz_pipeline load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset workiz_data
The duckdb destination used duckdb:/workiz.duckdb location to store data
Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

Copy
dlt pipeline workiz_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 job_all and team_all from the Workiz API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def workiz_source(api_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.workiz.com/api/v1/",
            "auth": {
                "type": "api_key",
                "api_key": api_token,
            },
        },
        "resources": [
            {"name": "job_all", "endpoint": {"path": "job/all/"}},
            {"name": "team_all", "endpoint": {"path": "team/all/"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="workiz_pipeline",
        destination="duckdb",
        dataset_name="workiz_data",
    )
    load_info = pipeline.run(workiz_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):

Copy
import dlt

data = dlt.pipeline("workiz_pipeline").dataset()
sessions_df = data.job_all.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM workiz_data.job_all LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("workiz_pipeline").dataset()
data.job_all.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 Workiz data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Troubleshooting

Authentication failures

If you receive 401 or 403 responses, verify that the Developer API add‑on is enabled, the API token and secret are correct, and that your user has permission to use the API. Regenerate the credentials in Settings > Integrations > Developer if needed.

Rate limits and throttling

The documentation mentions standard HTTP status codes. A 429 Too Many Requests response indicates you have hit a rate limit; implement exponential backoff and consult Workiz support for exact limits.

Pagination

List endpoints return paginated results (e.g., page, pageSize, total or an items envelope). Test the endpoint with valid credentials to discover the exact pagination fields and handle both envelope and top‑level array formats.

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.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack