ezeep Blue Python API Docs | dltHub

Build a ezeep Blue-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

ezeep Blue is a cloud printing platform providing REST APIs for managing printers, organizations, and print operations. The REST API base URL is https://api2.ezeep.com/ or https://printapi.ezeep.com/ and all API requests require a Bearer token in the Authorization header.

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 add "dlt[hub]" and start loading ezeep Blue data in under 10 minutes.


What data can I load from ezeep Blue?

Here are some of the endpoints you can load from ezeep Blue:

ResourceEndpointMethodData selectorDescription
printers/printing/v1/printers/GETresultsList all printers accessible with the current access token.
users/printing/v1/users/GETresultsList all users.
connectors/printing/v1/connectors/GETresultsList printer connectors.
drivers/printing/v1/drivers/GETresultsList available drivers.
groups/printing/v1/groups/GETresultsList all registered groups.
print_jobs/printing/v1/printjobs/GETresultsList print jobs with optional status filter.

How do I authenticate with the ezeep Blue API?

API requests require authentication via an OAuth2 access token provided in the Authorization header using the Bearer scheme. The token is obtained through OAuth2 flows, such as authorization code or client credentials.

1. Get your credentials

The ezeep Blue REST API uses OAuth 2.0 for authentication and does not use simple static API keys. To obtain production credentials (Client ID and Client Secret), you must request them from the ezeep team: 1. Navigate to the ezeep support portal. 2. Locate and fill out the API Request Form with your organization details. 3. Specify your required redirect URIs and scopes. 4. Once submitted, the ezeep Integration Team will process your request and provide you with a unique Client ID and Client Secret.

2. Add them to .dlt/secrets.toml

[sources.ezeep_blue_source] client_id = "your_client_id_here" client_secret = "your_client_secret_here" # Note: These are used to exchange for access tokens via OAuth2 flows (e.g., authorization_code or refresh_token).

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 init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run 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:

uv run dlthub ai toolkit install rest-api-pipeline

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 ezeep Blue 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:

uv run python ezeep_blue_pipeline.py

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

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

Inspect your pipeline and data:

uv run dlthub 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 /printing/v1/printers/ and /printing/v1/users/ from the ezeep Blue 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 ezeep_blue_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api2.ezeep.com/ or https://printapi.ezeep.com/", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "printers", "endpoint": {"path": "printing/v1/printers/", "data_selector": "results"}}, {"name": "print_jobs", "endpoint": {"path": "printing/v1/printjobs/", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="ezeep_blue_pipeline", destination="duckdb", dataset_name="ezeep_blue_data", ) load_info = pipeline.run(ezeep_blue_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("ezeep_blue_pipeline").dataset() sessions_df = data.printers.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM ezeep_blue_data.printers LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("ezeep_blue_pipeline").dataset() data.printers.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 ezeep Blue data to?

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

DestinationExample 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.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for ezeep Blue?

Request dlt skills, commands, AGENT.md files, and AI-native context.