Skip to main content
Use the cubic REST APIs to manage member seats and roles or export pull request analytics to your own tools. Both APIs use https://www.cubic.dev as the base URL.

​
Authentication and access

One key works for both APIs. Generate a personal key in Settings > API, CLI & MCP > cubic API. For automation that should not depend on one person, an organization admin can create an organization key with read or admin access in Settings > API, CLI & MCP. Send the key in the Authorization header as a bearer token. Analytics API keys that start with cak_ keep working with the Analytics API, but cubic no longer creates them. Personal keys use the key owner’s organization access, so reading Members data uses your existing permissions. An organization key reaches only its own organization, with read or admin access to its members. Updating a member needs an organization admin or an organization key with admin access, and an active Team, Pro, or Max subscription billed through cubic. Analytics access requires Pro or Max. See the Members guide or Analytics guide for key setup, pagination, and access requirements. Each endpoint page includes an authenticated request playground, response schemas, and code examples.

​
Other integrations

To use cubic from an IDE or coding agent, see the MCP server and CLI review guides.