Claude Code Analytics Admin API does not return subscription/OAuth users

[jbensamo]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

The Claude Code Analytics Admin API (GET /v1/organizations/usage_report/claude_code) only returns records with customer_type: "api". Users who authenticate to Claude Code via OAuth (claude.ai subscription login) do not appear in the API response at all.

The official documentation states that customer_type can be "api" or "subscription" and the FAQ explicitly says:

How are users identified in the data?

• user_actor: Contains email_address for users who authenticate via OAuth (most common)
• The customer_type field indicates whether the usage is from api customers (API PAYG) or subscription customers (Pro/Team plans).

However, no subscription records are ever returned. This has been reported before in #9700 and #20819, both of which were auto-closed by a bot without any response from Anthropic.

What Should Happen?

The API should return usage records for all Claude Code users in the organization, including those who authenticate via OAuth with their Claude.ai Team/Max subscriptions. These records should have customer_type: "subscription".

Evidence

Our organization ("Fi", org ID 0fb033ef-a1f3-466e-a534-70ff75162401) has 7 admin users and previously had ~15+ engineers using Claude Code via per-user API keys. We can confirm:

• December 2025: When engineers used API keys, we saw 9+ unique users in the API response (all customer_type: "api")
• February 2026: After migrating engineers to OAuth/subscription auth (and archiving the API keys), the API only returns 1-2 actors — effectively losing visibility into the entire team's usage
• Zero subscription records have ever been returned across any date range we've queried

We confirmed the org has active users via the /v1/organizations/users endpoint — the users exist, they're using Claude Code daily, but their usage simply doesn't appear in the analytics API.

Impact

This bug makes the Analytics API unusable for organizations whose engineers authenticate via OAuth, which the docs describe as "most common." The only workaround is to switch engineers back to API key auth, which bills against API credits instead of their subscription allowances — defeating the purpose of having subscriptions.

Steps to Reproduce

1. Have org members authenticate to Claude Code via Claude.ai (OAuth/subscription)
2. Use Claude Code throughout the day
3. Query GET /v1/organizations/usage_report/claude_code?starting_at=<date> with an Admin API key
4. Observe: only customer_type: "api" records appear; subscription users are missing

Previous Issues

• [BUG] Analytics API does not return Claude.ai subscription users #9700 — auto-closed after 60 days with no Anthropic response
• [Feature Request] Claude Code Analytics API missing subscription user usage data #20819 — auto-closed as duplicate of [BUG] Analytics API does not return Claude.ai subscription users #9700

Claude Model

Opus (claude-opus-4-6)

Claude Code Version

Latest

Platform

macOS

[github-actions]

Found 2 possible duplicate issues:

1. [BUG] Analytics API does not return Claude.ai subscription users #9700
2. [Feature Request] Claude Code Analytics API missing subscription user usage data #20819

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[nagliyvred]

we are seeing a similar issue, and this makes it really hard to understand spending. would be great to have this resolved

[nanno77]

Tripling down on this.... Went to build a spending reporting app and was shocked to find this information isn't available

[sergesyrota]

Same issue here: OAuth/subscription users are still missing from the Analytics Admin API on our side too, so this is clearly not an isolated case. At this point, months of silence and auto-closed reports make it look less like a bug and more like a deceptive, self-serving failure to provide basic transparency.

[joe-camp-15367]

I'm finding it frustratingly difficult to get basic per user usage/cost data for Enterprise subscriptions. Wouldn't most every organization be needing this? Are people solving this in some other way? This API would seem the simple answer to my needs, but...it doesn't work as advertised.

[holkeri]

Here's a response I got from Anthropic in January:

Claude.ai (where Pro and Team plans live) and the API Console at platform.claude.com are completely separate platforms with independent account systems and separate data stores. This is why your org IDs are different between the two platforms. They are distinct organizations, even if you use the same email address for both.

The Admin API key you created from platform.claude.com/settings/admin-keys is scoped to your Console API organization, so it can only return data for users within that Console organization, and cannot reach into claude.ai subscription organizations to retrieve that data. This is an architectural limitation, not a configuration issue on your end.

[matheuspalhares-ar]

@holkeri Do you know if is possible to bring the metrics information for claude.ai subscription? Because the only way to create a API key admin is inside platform.claude.com/settings/admin-keys website.

I did not find any other way to create an admin key in claude.ai.

[holkeri]

@matheuspalhares-ar, The way I understand it, the Analytics API doesn't support claude.ai.

Here's Anthropic's response to my follow-up question:

1. Why do the API docs at https://platform.claude.com/docs/en/build-with-claude/claude-code-analytics-api#dimensions say "subscription for Pro/Team customers" if the API doesn't support
   Pro/Team customers?

Ah good callout, that's actually incorrect information, I'll flag that to the docs team to get updated.

[xenofon-papadopoulos]

We need this too. Or at least add an export functionality to the cost explorer in claude.ai. It's been too hard to track usage since we moved to an enterprise plan.

[ASutterWork]

+1

[kohapple]

Adding a Team-plan perspective on the same root problem — per-user usage visibility for non-API-key (subscription/OAuth) users.

Team plan admins are hit harder than Enterprise, because we don't have access to the Admin API at all. Our only tools are two CSV exports from the admin Analytics page, and both are structurally unable to answer "who uses heavily?" and "who doesn't use their seat?":

1. Spend Report CSV — overage-only. Users within their seat quota appear as $0 or are absent entirely. No date column.
2. Claude Code team export — Lines this Month only. Silently undercounts every non-coding use case (security review, threat modeling, architecture design, pentest analysis, code critique, documentation, planning).

The data clearly exists — the admin Analytics page renders daily aggregate charts (unique users, sessions, lines of code per day) that can only be computed from per-user daily data. It's just not exposed at per-user granularity anywhere a Team plan admin can reach.

Concrete example from my team this month (identifiers redacted):

Metric	Value
Lines of code this month	63
Overage spend (90 days)	$76.56 — highest on team
Requests	660
Prompt tokens	~84M

By the Lines export this user barely exists. By the Spend export they look like the most reckless spender on the team. Reality: heavy, legitimate non-coding usage (review, design, threat modeling). No export I have access to can represent this user honestly — and this is exactly the kind of user an admin most needs visibility into for capacity and budget planning.

The pattern across #9700, #20819, and now this issue is consistent: per-user usage for subscription/OAuth users is the single most-requested admin gap, and each prior issue has been auto-closed without an Anthropic response. Would appreciate even a one-line acknowledgement on direction here — is this on the roadmap, declined, or still unscoped?

For what it's worth, the Team-plan version of this ask is small in scope: a per-user, per-day CSV export (email, date, product, model, requests, tokens, sessions) on the existing admin Analytics page would be sufficient. No API required.

[denisurbanavicius]

+1 We have a lot of developers on subscription plan that we can't track if the seat is being used correctly since all our usage reports are $0.00 for them. They are also missing in the tokens report. We have gone completely blind metrics-wise.