EZShift Python API Docs | dltHub
Build a EZShift-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
EZShift is a workforce scheduling and time and attendance management platform for complex operations. The REST API base URL is The documentation site api.ezshift.com does not provide public access to reference specifications. and Public REST API documentation is not currently accessible to determine authentication requirements..
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 EZShift data in under 10 minutes.
What data can I load from EZShift?
Here are some of the endpoints you can load from EZShift:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| employees | /employees | GET | Retrieve list of employees | |
| schedules | /schedules | GET | Retrieve shift schedules | |
| shifts | /shifts | GET | Retrieve individual shift records | |
| departments | /departments | GET | Retrieve organizational departments | |
| skills | /skills | GET | Retrieve employee skills and capabilities |
How do I authenticate with the EZShift API?
Public REST API documentation for EZShift is not currently accessible to verify specific authentication mechanisms, headers, or token formats.
1. Get your credentials
EZShift provides API access as a professional integration service rather than via a self-service public developer portal. To obtain credentials: 1. Contact your EZShift Account Manager to verify if your subscription tier is eligible for API access. 2. Upon approval, you will receive secure communication containing your client integration credentials (typically an API Key or Client ID/Secret pair). 3. Manage or rotate these credentials directly through the administration panel provided by your account manager, or via the secure channel established during the integration setup process.
2. Add them to .dlt/secrets.toml
[sources.ezshift_source] Not available = "REPLACE_ME"
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 harness:
dlthub 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:
dlthub 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 EZShift 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 ezshift_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline ezshift_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset ezshift_data The duckdb destination used duckdb:/ezshift.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline ezshift_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 employees and schedules from the EZShift 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 ezshift_source(not_available=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "The documentation site api.ezshift.com does not provide public access to reference specifications.", "auth": {"type": "bearer", "token": not_available}, }, "resources": [ {"name": "employees", "endpoint": {"path": "employees"}}, {"name": "schedules", "endpoint": {"path": "schedules"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="ezshift_pipeline", destination="duckdb", dataset_name="ezshift_data", ) load_info = pipeline.run(ezshift_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("ezshift_pipeline").dataset() sessions_df = data.employees.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM ezshift_data.employees LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("ezshift_pipeline").dataset() data.employees.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 EZShift 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.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
dlthub ai toolkit data-exploration install dlthub ai toolkit dlthub-platform install
Was this page helpful?
Community Hub
Need more dlt context for EZShift?
Request dlt skills, commands, AGENT.md files, and AI-native context.