DigiUsher - Connecting a Claude.ai account

Connect your Claude.ai Enterprise organization to DigiUsher with an Analytics API key to track AI spend and usage per user and per model.

Overview

To connect your Claude.ai Enterprise organization to DigiUsher, create an Analytics API key in the settings of your organization. Then enter that key in DigiUsher. This page gives the access that DigiUsher asks for, the reason for that access, and the credential that you enter.

Claude Enterprise plan is required

This feature does not work on the Teams plan or with an individual account. You need a Claude Enterprise plan with at least one member that has the Primary Owner role.

Summary of Access Required

Component	Details
Identity	Analytics API key for programmatic access only
Access level	Read-only. Engagement and cost data of the whole organization
Data	Activity, cost, and token usage of each user
Scope	Organization-wide

Capability	What It Provides
Per-user cost	Spend per seat user, alongside the undiscounted list price for the same usage
Per-user token usage	Token consumption per user across models and product surfaces
Product surface breakdown	Spend and usage broken down by Claude product (chat, Claude Code and others)
Model breakdown	Cost and usage split by `product`, `model`, `context_window`, `speed`, and `inference_geo`

DigiUsher cannot send messages, cannot consume tokens, and cannot create, change, or delete a resource in your Claude.ai organization.

Seat users only

The analytics data covers the seat users of your organization. It does not contain the usage of direct API keys and of automation traffic.

Prerequisites

Information to Gather

Item	How to Find	DigiUsher Field
Analytics API Key	claude.ai > Organization settings > API > Create key. The page shows the key one time only, so save it in a safe place.	`api_key`

Roles Required by the Person Performing Setup

Role / Permission	Why
Primary Owner on the Claude.ai organization	Only the Primary Owner can create Analytics API keys in Organization settings.

Network & Email Access (For Regulated Environments)

If your organization restricts outbound internet access or email domains, make sure that these two items are in place before you start:

Domain allowlist. Add *.digiusher.com to the allowlist of your network and your firewall. The users of your organization can then open the DigiUsher platform in their browsers.
Email allowlist. Add digiusher.com as a permitted sender domain in your email security gateway. DigiUsher sends onboarding confirmations, alerts, and reports from @digiusher.com addresses.

Setup

Make Sure You Have the Enterprise Plan and the Primary Owner Role

An Analytics API key needs the Claude Enterprise plan and the Primary Owner role.

Sign in to claude.ai with an account that has the Primary Owner role.
Make sure that your organization has the Claude Enterprise plan. If you do not know the plan, write to your Claude account team.
Make sure that your role is Primary Owner. If it is not, ask the Primary Owner to do the next steps or to give you the role.

Don't see the API section in Organization settings?

If the API section does not appear under Organization settings, your organization does not have the Enterprise plan, or your account does not have the Primary Owner role.

Create an Analytics API Key

Create a separate Analytics API key for DigiUsher. DigiUsher uses this key for read operations only.

In claude.ai, open Organization settings > API and enable the public API access.
Create an Analytics API key with the scope read:analytics. Give the key a name that you know again, for example digiusher-analytics.
Copy the value of the new key.

Save your credential

CAUTION: Copy the Analytics API key now and save it in a safe place. The page shows the key one time only, and you cannot read it again. You enter this key in DigiUsher in the next section.

Connect in DigiUsher

In DigiUsher, go to Connectors > Add Source and select Claude.ai Enterprise. On the Configure step, enter the values in the table. Then go to Connect and click Connect source:

Field	Where to Find
Display Name	Any label you prefer, for example `Claude Production`
Analytics API Key	The key from the step before

At the connection, DigiUsher makes sure that the key works and starts to read the usage data of your organization. The first sync reads the last 31 days. It extends this period to whole calendar months, and it never reads a date before January 1, 2026, because the Analytics API returns no data before that date. Every sync after the first one reads the current calendar month again. The values of the days that are already loaded therefore change when Claude finalizes them.

Data refresh cadence

Claude reports the usage in buckets of one day, and not in real time. The most recent day can be absent.

Setup Checklist

The organization has the Claude Enterprise plan
You have the Primary Owner role on the organization
Analytics API key created in claude.ai Organization settings > API
Analytics API key saved in a safe place
Connection details entered in DigiUsher
*.digiusher.com in the allowlist of your network and firewall (if your organization restricts this)
digiusher.com in the allowlist of permitted sender domains in your email security gateway (if your organization restricts this)

Security

What DigiUsher CAN Access (Read-Only)

Spend, token counts, the model used, and the product surface breakdown of each user
The email address and the name of a user, which DigiUsher needs to attribute the cost to the correct user

What DigiUsher CANNOT Do

Send a message or consume tokens in your organization
Create, change, or delete an API key, a member, or a workspace
Read message content, prompts, or completions
Read or change the billing configuration, the payment methods, or the rate limits
Buy a product or change your account

Monitoring

Open Organization settings > API in claude.ai to see the keys that exist and the last time each key was used. Delete every key that you do not know.

Credential Rotation

In claude.ai, go to Organization settings > API and create a new Analytics API key.
Enter the new key in DigiUsher immediately.
Delete the old key in Organization settings.

Avoid ingestion gaps

Create the new key and enter it in DigiUsher before you delete the old key. This prevents an interruption of the data collection.

Make sure that your organization has the Claude Enterprise plan. The Teams plan gives no analytics data for each user.
Make sure that the Primary Owner created the key, and that the key still exists.
Create the key again in Organization settings > API and enter it again in DigiUsher.

Enterprise plan required

If you get an error about the plan, ask your Anthropic account team whether your organization has the Enterprise plan.

Data lower than expected or incomplete

Claude reports the usage in buckets of one day. The current day is therefore not available yet.
No data exists before January 1, 2026. DigiUsher never asks for an earlier date.
Every sync reads the current calendar month again. The values of the recent days therefore change when Claude finalizes them.

API or automation spend is missing

These analytics cover the seat users only. They do not contain the usage of direct API keys or of automation traffic.

Need Help?

If this page does not answer your question, write to DigiUsher support at support@digiusher.com. The team will help you.

Connecting a Claude.ai account