Umbrella Cost Python API Docs | dltHub

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

Last updated:

Umbrella Cost is a FinOps platform providing cloud cost and usage data analysis across multiple cloud providers. The REST API base URL is https://api.umbrellacost.io and all requests require both a Bearer token and a structured apikey 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 Umbrella Cost data in under 10 minutes.


What data can I load from Umbrella Cost?

Here are some of the endpoints you can load from Umbrella Cost:

ResourceEndpointMethodData selectorDescription
cost_usage/api/v2/invoices/cost-and-usageGETdataRetrieves cost and usage data
usage_assets/api/v2/usage/assetsGETRetrieves assets information
global_mappings/api/v2/business-mapping/global-mappingsGETRetrieves global mappings
budgets/api/v2/budgetsGETRetrieves budgets
recommendations/api/v2/recommendations/listPOSTRetrieves recommendations

How do I authenticate with the Umbrella Cost API?

Requests require both an 'Authorization' header containing a Bearer token and an 'apikey' header with a specific structured format (user_key:account_id:).

1. Get your credentials

To obtain API credentials for Umbrella Cost (UM 2.0): 1. Perform a POST request to https://api.umbrellacost.io/api/v1/authentication/token/generate with your username and password in the JSON body to retrieve your User Key. 2. Use the User Key to call the Payer Accounts endpoint (GET /api/v2/user-management/accounts/data-access/payer-accounts) to retrieve your Account ID. 3. Optionally call the Cost Centers list endpoint (GET /api/v2/user-management/cost-centers/management/list) to get a specific Cost Center ID, or leave blank to use all. 4. Construct the final API Key in the format: user-key:account-id

. Note that API requests also require a separate Bearer Token in the Authorization header.

2. Add them to .dlt/secrets.toml

[sources.umbrella_cost_source] api_key = "user-key:account-id:cost-center-id" bearer_token = "your_bearer_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 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 Umbrella Cost 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 umbrella_cost_pipeline.py

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

Pipeline umbrella_cost_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset umbrella_cost_data The duckdb destination used duckdb:/umbrella_cost.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 /api/v2/user-management/accounts/data-access/payer-accounts and /api/v2/invoices/cost-and-usage from the Umbrella Cost 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 umbrella_cost_source(apikey=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.umbrellacost.io", "auth": {"type": "bearer", "token": apikey}, }, "resources": [ {"name": "cost_usage", "endpoint": {"path": "api/v2/invoices/cost-and-usage", "data_selector": "data"}}, {"name": "usage_assets", "endpoint": {"path": "api/v2/usage/assets"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="umbrella_cost_pipeline", destination="duckdb", dataset_name="umbrella_cost_data", ) load_info = pipeline.run(umbrella_cost_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("umbrella_cost_pipeline").dataset() sessions_df = data.cost_usage.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM umbrella_cost_data.cost_usage LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("umbrella_cost_pipeline").dataset() data.cost_usage.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 Umbrella Cost 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 Umbrella Cost?

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