DigiUsher - Connecting a ClickHouse Cloud account

Connect your ClickHouse Cloud organization to DigiUsher with an organization ID and an API key (key ID + secret) to track usage-based spend across your ClickHouse Cloud services.

Overview

To onboard your ClickHouse Cloud account to DigiUsher, you create an API key in the ClickHouse Cloud console and provide it — along with your organization ID — to DigiUsher. DigiUsher uses these credentials to read your organization's usage cost through the ClickHouse Cloud API. This document describes exactly what access is requested, why it is needed, and what credentials to provide.

Summary of Access Required

Component	Details
Identity	ClickHouse Cloud API key — key ID + secret, programmatic access only
Access level	Read — organization level billing data
Data	Usage cost per service and per metric, per day
Scope	A single ClickHouse Cloud organization (billing scope only)

Capability	What It Provides
Spend by service	Cost attributed to each ClickHouse Cloud service in the organization
Spend by metric	Compute, Storage, Backup, Initial Load, and Data Transfer costs
Usage quantities	ClickHouse Credits (CHC) consumed per metric

DigiUsher cannot connect to your ClickHouse services, query your data, modify services, or change any ClickHouse Cloud configuration.

Prerequisites

Information to Gather

Item	How to Find	DigiUsher Field
Organization ID	ClickHouse Cloud console → Organization → Details	`Organization ID`
API Key ID	Shown when you create an API key (see Setup below)	`API Key ID`
API Key Secret	Shown once when the API key is created	`API Key Secret`

Roles Required by the Person Performing Setup

Role / Permission	Why
Admin (or a role that can create API keys with read access to usage) on the ClickHouse Cloud organization	Only these roles can create organization API keys.

Network & Email Access (For Regulated Environments)

If your organization restricts outbound internet access or email domains, ensure the following are in place before starting:

Domain allowlist: Add *.digiusher.com to your network/firewall allowlist so that users in your organization can access the DigiUsher platform from their browsers.
Email allowlist: Add digiusher.com as an approved sender domain in your email security gateway. DigiUsher sends onboarding confirmations, alerts, and reports from @digiusher.com addresses.

Setup

Open API Keys

In the ClickHouse Cloud console, open Organization → API keys.

ClickHouse Cloud API keys page

Create an API Key

Click New API key and configure it for read access to usage cost.

Enter a recognizable Name, for example digiusher-billing.
Assign the Admin role (or a read-only role that includes access to organization usage).
Click Generate API key.

Create a ClickHouse Cloud API key

Copy the Key ID and Secret

When the key is created, ClickHouse Cloud shows the Key ID and Key Secret. Copy both.

Save your credential

The Key Secret is shown only once at creation and cannot be retrieved again. Copy and store it securely — you will enter it into DigiUsher in the next section. If you lose it, delete the key and create a new one.

Find the Organization ID

Open Organization → Details and copy the Organization ID. This is the organization whose usage cost DigiUsher will read.

Confirm What You Have

Before moving on, verify:

You have the Organization ID (from Step 4).
You have the API Key ID and API Key Secret (from Steps 2–3).

Connect in DigiUsher

After completing the steps above, enter the following into DigiUsher to complete the connection:

Field	Where to Find
Name	Any label you prefer, for example `ClickHouse Cloud Production`
Organization ID	From Step 4
API Key ID	From Step 2
API Key Secret	From Step 3

When you connect, DigiUsher validates the credentials against your organization and begins importing usage-cost data. The first sync backfills recent history; after that, DigiUsher ingests new data daily.

Verification Checklist

ClickHouse Cloud organization with usage data
Admin role (or a role that can create API keys) on the organization
Organization ID located and copied
API key created with read access to usage
Key ID and Key Secret saved securely
Organization ID, Key ID, and Key Secret entered in DigiUsher
*.digiusher.com allowlisted in your network/firewall (if applicable)
digiusher.com allowlisted as an approved sender domain in your email security gateway (if applicable)

Security

What DigiUsher CAN Access (Read-Only)

Usage cost per service, per metric, per day
Usage quantities in ClickHouse Credits (Compute, Storage, Backup, Initial Load, Data Transfer)

What DigiUsher CANNOT Do

Connect to your ClickHouse services or query your data
Create, modify, or delete services
Create, rotate, or delete API keys
View or modify payment methods, plan settings, or billing contacts
Make purchases or any changes to your account

Monitoring

Review keys at Organization → API keys. Confirm which keys exist and when they were last used. Remove any keys you no longer recognize.

Credential Rotation

In the ClickHouse Cloud console, create a new API key.
Update the Key ID and Key Secret in DigiUsher immediately.
Delete the old API key from the console.

Avoid ingestion gaps

Always create the new key and update DigiUsher before deleting the old one to avoid an interruption in data ingestion.

Revocation

Delete the API key at Organization → API keys. This immediately invalidates the key and stops all access. DigiUsher will no longer be able to ingest billing data until a new key is provided.

Troubleshooting

401 / 403 / invalid key

Confirm you copied both the Key ID and the Key Secret correctly, that the key belongs to the organization whose ID you entered, and that the key has not been deleted. Re-create the API key in the ClickHouse Cloud console and re-enter both values in DigiUsher.

Connecting a ClickHouse Cloud account