Skip to main content
Telara

Integrations / Anthropic Admin API

Anthropic Admin API logo

Anthropic Admin API

Anthropic organization Admin API — workspace, member, API key management plus Usage & Cost reporting for per-workspace / per-key token spend governance.

API key
Spend

What Telara does

Capability matrix

Indexes NoTracks spend YesDiscovers shadow AI NoRuns actions NoReal-time events No

Before you connect

Prerequisites

This connector requires an Anthropic Admin API key (sk-ant-admin...), issued from the Claude Console under Settings → Admin keys (admin role required). A standard Anthropic API key cannot access org-level usage data. For direct Claude API usage tracking, use the Anthropic Direct connector instead.
An Anthropic Organization with admin API access.
An organization admin who can issue the admin key.

Vendor setup

Get the credential

1
Open organization admin keys
In the Anthropic Console, open the organization admin / API keys surface (not a workspace member key).
2
Issue the admin key
Create the organization admin key Telara asks for. Paste it under Settings → Integrations → Anthropic Admin.

In Telara

Connect in Telara

API key

Anthropic Admin API key (prefix `sk-ant-admin...`). DIFFERENT from a standard Anthropic API key — the admin key is gated by the `admin` organization role and is the ONLY way to read the Usage & Cost endpoints. Only org members with the admin role can provision admin keys through the Claude Console (`/settings/admin-keys`). Admin keys cannot be minted via this API itself — they are issued only through the Console for security reasons. Every request additionally requires the `anthropic-version: 2023-06-01` header. The key is sent unprefixed in `x-api-key` (NOT `Authorization: Bearer ...`, which is the OpenAI shape). On Claude Platform on AWS, only workspace endpoints are exposed; usage, cost, members, and API key management are not available — connector should degrade gracefully.

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • Admin Api Key

Spend

What gets measured

Resolution: Aggregated buckets.

Attribution: Matched to people by email.

How far back vendor history goes is not published uniformly for this connector.

  • input_tokens_uncached
    tokens
  • input_tokens_cache_read
    tokens
  • input_tokens_cache_creation
    tokens
  • output_tokens
    tokens
  • server_tool_use_web_search_count
    requests
  • cost_amount_cents
    usd
  • claude_code_sessions
    count
  • lines_accepted_added
    lines
  • lines_accepted_deleted
    lines
  • commits_created
    count
  • pull_requests_created
    count
  • edit_tool_accepted
    count
  • edit_tool_rejected
    count
  • estimated_cost_cents
    count — Estimated Claude Code cost in USD cents (divide by 100). Advisory when OTLP telemetry is connected.

Sync

Freshness & sync

Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

This connector requires an Anthropic Admin API key (sk-ant-admin...), issued from the Claude Console under Settings → Admin keys (admin role required). A standard Anthropic API key cannot access org-level usage data. For direct Claude API usage tracking, use the Anthropic Direct connector instead.

Honesty

Known limitations

Member API keys are the wrong class for this connector.
Usage visibility follows the organization the key belongs to — a second org needs a second connection.