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 onboard your Claude.ai Enterprise organization to DigiUsher, you create an Analytics API key in your organization settings and provide it to DigiUsher. This document describes exactly what access is requested, why it is needed, and what credential to provide.

Claude Enterprise plan is required

This feature is not available on the Teams plan or individual accounts. You need a Claude Enterprise plan with at least one member holding the Primary Owner role.

Summary of Access Required

Component	Details
Identity	Analytics API key — programmatic access only
Access level	Read-only — organization-wide engagement and cost data
Data	Per-user activity, cost, and token usage
Scope	Organization-wide

Capability	What It Provides
Per-user cost	USD spend per seat user (post-discount, pre-credit)
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 model

DigiUsher cannot send messages, consume tokens, or create, modify, or delete any resources in your Claude.ai organization.

Seat users only

Analytics data covers seat users in your organization. Usage from direct API keys and automation traffic is not included.

Prerequisites

Information to Gather

Item	How to Find	DigiUsher Field
Analytics API Key	claude.ai > Organization settings > API > Create key (shown once at creation — store securely)	`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, 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

Confirm Enterprise Plan & Primary Owner Access

Analytics API keys require the Claude Enterprise plan and the Primary Owner role.

Sign in to claude.ai with an account that holds the Primary Owner role.
Confirm your organization is on the Claude Enterprise plan. If you are unsure, contact your Claude account team.
Confirm your role is Primary Owner. If it is not, ask the existing Primary Owner to either perform the next steps or delegate access.

Don't see the API section in Organization settings?

If the API section is not visible under Organization settings, your organization is not on the Enterprise plan or your account does not hold the Primary Owner role.

Create an Analytics API Key

Create a dedicated Analytics API key for DigiUsher. This key is used in a read-only manner.

In claude.ai, open Organization settings > API and enable public API access.
Create a Analytics API key (having the read:analytics scope) and give it a recognizable name, for example digiusher-analytics.
Copy the generated key value.

Save your credential

The Analytics API key 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.

Copy and Store the Key

Keep the key value ready — you will enter it into DigiUsher in the next section.

Connect in DigiUsher

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

Field	Where to Find
Connection Name	Any label you prefer, for example `Claude Production`
Analytics API Key	The key created in Step 2

When you connect, DigiUsher validates the key and begins ingesting your organization's usage data. The first sync backfills up to 365 days of historical data; after that, DigiUsher refreshes data approximately every day.

Data refresh cadence

Usage data is not real-time, so the most recent hours may not yet be reflected. Cost and usage figures for a given date are typically not fully settled until roughly 30 days after the usage occurred.

Verification Checklist

Organization is on the Claude Enterprise plan
You hold the Primary Owner role on the organization
Analytics API key created in claude.ai Organization settings > API
Analytics API key saved securely
Connection details 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)

Per-user spend, token counts, model used, and product surface breakdown
User email and name (for cost attribution to the correct user)

What DigiUsher CANNOT Do

Send messages or consume tokens against your organization
Create, modify, or delete API keys, members, or workspaces
Access message content, prompts, or completions
View or modify billing settings, payment methods, or rate limits
Make purchases or any changes to your account

Monitoring

Review the API keys in your claude.ai Organization settings > API to confirm which keys exist and when they were last used. Remove any keys you no longer recognize.

Credential Rotation

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

Avoid ingestion gaps

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

Confirm your organization is on the Claude Enterprise plan. The Teams plan does not expose per-user analytics data.
Confirm the key was created by the Primary Owner and that it has not been deleted or revoked.
Re-create the key in Organization settings > API and re-enter it in DigiUsher.

Enterprise plan required

If you see a plan-related error, confirm your Anthropic account team has provisioned the Enterprise plan for your organization.

Data lower than expected or incomplete

Data refreshes approximately every 4 hours. Usage from recent hours may not yet appear.
Cost figures for a given date may not be fully settled for up to 30 days after the usage date.

API or automation spend is missing

These analytics cover seat users only. Usage attributed to direct API keys or automation traffic is not included.

Need Help?

If you encounter any issues not covered above, contact DigiUsher support at support@digiusher.com and the team will help you get set up.

Connecting a Claude.ai account