Hydra Cloud Python API Docs | dltHub
Build a Hydra Cloud-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Hydra Cloud API provides endpoints for job batches and records, requiring user authentication and specific headers. Key endpoints include job batches and records retrieval. Documentation is available at http://api.doc.hydra.cloud/. The REST API base URL is https://api.hydra.cloud/v1 and All requests require an etask-auth-token header (token obtained via login); company-mode also requires etask-company 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 pip install "dlt[workspace]" and start loading Hydra Cloud data in under 10 minutes.
What data can I load from Hydra Cloud?
Here are some of the endpoints you can load from Hydra Cloud:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| customers | /v1/customers | GET | List customers for authenticated user/company (returns array of customer objects) | |
| customers_find | /v1/customers/{customerID} | GET | Get single customer object (returns object with fields id, companyId, companyName, name, alias, website, status) | |
| documents_find | /v1/documents/{documentID} | GET | Get document metadata (returns object with id, companyId, etc.) | |
| documents_download | /v1/documents/{documentID}/download | GET | Download document binary (content-type application/pdf or original) | |
| projects_stream | /v1/projects/stream | GET | Stream/return projects (supports etask-request headers for pagination/filters) | |
| users | /v1/users | GET | List users for the company (returns array of user objects) | |
| team | /v1/team | GET | List team members (returns array) | |
| timesheets | /v1/timesheets | GET | List time logs (supports stream variant /v1/timesheets/stream) | |
| auth_company | /v1/auth/{companyId}/{apiKey} | GET | Obtain authentication token for company API Key (returns token string) | |
| auth_platform_login | /v1/login/{username}/{password} | GET | Obtain authentication token for platform user (returns token string) |
How do I authenticate with the Hydra Cloud API?
Obtain an authentication token by calling the login endpoints (platform user: GET /v1/login/{username}/{password} or mobile POST /v1/login; company: GET /v1/auth/{companyId}/{apiKey} or POST /v1/auth). Include the returned token in every subsequent request in the etask-auth-token header. For company-mode also include etask-company with the company id; for user-mode include etask-user.
1. Get your credentials
- Log into Hydra PSA web application as company administrator.
- Go to Company Preferences (Company Administration) and generate an API Key (or regenerate if exists).
- Note the company id shown in administration and copy the generated apiKey. Use these to call GET /v1/auth/{companyId}/{apiKey} (or POST /v1/auth) to obtain etask-auth-token.
2. Add them to .dlt/secrets.toml
[sources.hydra_cloud_source] company_id = "your_company_id" api_key = "your_api_key"
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 Hydra Cloud 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 hydra_cloud_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline hydra_cloud_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset hydra_cloud_data The duckdb destination used duckdb:/hydra_cloud.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline hydra_cloud_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 customers and projects from the Hydra Cloud 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 hydra_cloud_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.hydra.cloud/v1", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "customers", "endpoint": {"path": "v1/customers"}}, {"name": "projects", "endpoint": {"path": "v1/projects/stream"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="hydra_cloud_pipeline", destination="duckdb", dataset_name="hydra_cloud_data", ) load_info = pipeline.run(hydra_cloud_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("hydra_cloud_pipeline").dataset() sessions_df = data.customers.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM hydra_cloud_data.customers LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("hydra_cloud_pipeline").dataset() data.customers.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 Hydra Cloud 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 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 Hydra Cloud?
Request dlt skills, commands, AGENT.md files, and AI-native context.