Configuring Claude Code (Enterprise Analytics API)

LinearB supports multiple Claude integration paths under the Claude Code integration. Each path is designed for a different type of data collection.

• Claude Code Admin API — Use this path for Claude Code activity data collected through the Claude Admin API.
• Claude Enterprise Analytics API — Use this path for Claude usage and adoption reporting through Anthropic’s Analytics API.

The Enterprise Analytics API path is intended for customers who need Claude usage visibility without replacing or confusing other Claude connector workflows.

Use this connector when:

• Your organization has a Claude Enterprise license.
• You need Claude usage metrics through Anthropic’s Analytics API.
• You want organization-level Claude usage and adoption reporting.
• You do not need detailed tool-event telemetry from this connector path.

• LinearB role: Company Admin.
• Anthropic access: Primary Owner or equivalent admin access.
• Required scope: An Anthropic API key with read:analytics access.
• License: Claude Enterprise.

1. Log in to your Anthropic admin environment.
2. Create or retrieve an API key for Analytics API access.
3. Confirm that the key includes the read:analytics scope.
4. Store the key securely. You will need it when configuring the connector in LinearB.

1. In LinearB, go to Settings → Company Settings → AI Tools.
2. Open Claude Code.
3. Select Add connector.
4. Select Analytics API as the connector type.
5. Enter the required Anthropic API key and organization details.
6. Click Save.

After saving the connector, LinearB validates the configuration and begins collecting available Claude analytics data according to the connector’s data availability rules.

The Analytics API path provides Claude usage and adoption reporting based on the data available through Anthropic’s analytics endpoints.

• Analytics data is oriented toward usage and adoption summaries.
• Anthropic documents a 3-day data delay for this path.
• Available analytics data begins from January 1, 2026.
• Data should not be treated as near-real-time telemetry.

• Organization-level Claude analytics summaries.
• User-level usage summaries.
• Claude adoption and activity reporting.

After data is collected and processed, Claude usage data may appear in the following LinearB areas:

• AI Analytics
• AI Insights
• AI Adoption
• AI Tools Usage, where available

Data availability depends on your LinearB configuration, connector status, and the data returned by Anthropic.

If the connector cannot be saved or Claude analytics data does not appear as expected, check the following:

• Confirm that the feature is enabled for your organization.
• Confirm that your Anthropic account includes Claude Enterprise access.
• Verify that the API key includes the required read:analytics scope.
• Confirm that the key was created by a Primary Owner or equivalent Anthropic admin.
• Allow for the documented Analytics API data delay before validating recent activity.
• Confirm that you selected the correct Claude connector type in LinearB.

• The Analytics API path is designed for usage and adoption summaries, not detailed tool-action attribution.
• Analytics data is delayed and should not be treated as real-time data.
• Available historical data depends on Anthropic’s Analytics API availability and retention behavior.
• Connector requirements differ between Admin API and Analytics API paths.

• Claude Code Admin API

Use the connector path that matches the type of Claude data your organization needs to collect.