Docs / Data sources / Claude Enterprise (Analytics API)

Claude Enterprise (Analytics API)

Business software

Built when you ask for it

Sync your Claude Enterprise organization's usage analytics into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Claude Enterprise connector syncs your organization's Claude analytics into analytics-ready tables in your data warehouse. Pull each person's daily activity in chat, Claude Code, Cowork and the other Claude products, organization-wide active users and seats, and usage of projects, skills, connectors, plugins and artifacts from Anthropic's Claude Enterprise Analytics API, with Ingest handling auth, pagination, and retries so the tables stay current. It uses an Analytics API key, separate from the Admin API key the Anthropic (Admin API) connector reads with.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Per-person daily activity
  • Active users and seats
  • Projects, skills and connectors
  • Plugins and artifacts
  • Token usage and cost

How it gets built

  1. Choose Claude Enterprise (Analytics API) when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Claude Enterprise (Analytics API)'s documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Claude Enterprise (Analytics API) itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

Analytics API key (x-api-key header). Only the primary owner of your Claude Enterprise organization can create the key: in claude.ai, open Organization settings > API, enable public API access, and create an Analytics API key. An Admin API key from the Claude Console can't call these endpoints.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Claude Enterprise (Analytics API) connector?
Not as a finished connector yet. Ingest builds it from Claude Enterprise (Analytics API)'s own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Claude Enterprise (Analytics API) data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Claude Enterprise (Analytics API) API documentation: https://platform.claude.com/docs/en/manage-claude/analytics-api

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Salesforce, Airtable, Clockify, Facebook Ads.

Request Claude Enterprise (Analytics API)