Analytics APIs

Anthropic provides two analytics APIs, and which one you use depends on which Claude product your organization manages:

• The Claude Code Analytics API reports daily Claude Code productivity metrics for organizations that use the Claude Platform. It is part of the Admin API and uses an Admin API key.
• The Claude Enterprise Analytics API reports organization-wide engagement, adoption, and cost data across Claude products (chat, projects, Claude Code, and more) for Claude Enterprise organizations. It uses an Analytics API key created in claude.ai.

The two APIs use different key types, created in different places by different roles. This page describes which API fits your organization and how to create the right key.



Which API do you need?

The key types are not interchangeable: an Admin API key cannot call the Claude Enterprise Analytics API, and an Analytics API key cannot call the Admin API. Both APIs appear under the Admin API reference, but they are separate APIs with separate key types. If your organization uses both the Claude Platform and Claude Enterprise, you can provision both keys and use each API for its own data.



Get access to the Claude Code Analytics API

The Claude Code Analytics API is available to every organization with access to the Admin API, and is free to use.

For the available metrics, request parameters, and response schema, see the Claude Code Analytics API guide and the API reference.



Get access to the Claude Enterprise Analytics API

The Claude Enterprise Analytics API is available to Claude Enterprise organizations. Engagement and adoption data is available on all Enterprise plans. The cost and usage endpoints apply to usage-based Enterprise plans; for seat-based Enterprise plans, they reflect usage credits only.

The Claude Enterprise Analytics API provides:

• User activity: per-user daily metrics across chat (conversations, messages, projects, files, artifacts), Claude Code (sessions, commits, pull requests, lines of code, tool actions), and other Claude products
• Activity summaries: organization-level daily, weekly, and monthly active users, seat counts, and pending invites
• Project, skill, and connector usage: adoption breakdowns for chat projects, skills, and connectors
• Cost and usage reports: per-user and organization-level token usage and cost over time (usage-based Enterprise plans)

For endpoint details, parameters, and response schemas, see the Claude Enterprise Analytics API reference. The following sections cover data freshness, metric definitions, and operational guidance that apply across those endpoints.



Data availability and freshness

Claude Enterprise Analytics API data is available for dates on or after January 1, 2026.

Engagement and adoption endpoints (user activity, summaries, projects, skills, connectors) return a per-day snapshot for the date you specify. Data for a given day is aggregated at 10

Cost and usage endpoints follow a different freshness model. Data is typically available within four hours of the underlying usage but may take up to 24 hours. Values for a given date can be revised for up to 30 days as late events arrive and reconciliation runs. For invoicing-grade totals, query dates at least 30 days in the past.



How metrics are defined

Active users. A user counts as active for a day if any of the following is true: they sent at least one chat message in Claude, they had at least one Claude Code session (local or remote) associated with your Claude Enterprise organization that included tool use or git activity, or they had at least one Cowork session with tool use or message activity.

Per-product metric blocks. Per-product metric objects (for example, Office Agent or Cowork metrics on a user-activity record) are always present on every record. Organizations without usage of that product see all-zero values rather than null.

Connector names. Connector names are normalized across sources. For example, Atlassian MCP server, mcp-atlassian, and atlassian_MCP all appear as atlassian in the connector usage endpoint.



Working with the API

Pagination cursors are bound to the query that issued them. On the cost and usage endpoints, do not change query parameters mid-sequence: if you change products[], group_by[], order_by, the date range, or any filter and pass an old cursor, the request returns a 400 error. To change parameters, restart from the first page without a cursor.

List parameters use bracket notation. Repeat the parameter for each value, for example products[]=chat&products[]=claude_code.

Amount fields are decimal strings in cents. Currency amounts are returned as decimal strings such as "41280.000000" (which represents $412.80). To convert to dollars, parse as a decimal and divide by 100. Avoid binary floating-point parsing for values that may exceed several million dollars.

Rate limits apply at the organization level, not per key, with a default of 60 requests per minute across all endpoints in this API. If that is not sufficient for your use case, contact your Anthropic account team to discuss adjusting the limit.



Known limitations

If your organization uses Claude Code through Amazon Bedrock, the Claude Enterprise Analytics API does not return Claude Code activity for that usage.



Next steps