Introduction

Cube’s HTTP APIs — query your data with the Core Data API, stream agent conversations with the AI API, and manage Cube with the Platform API.

Cube exposes three HTTP API families, each for a different job and with slightly different authentication:

API	What it’s for	Authentication
Core Data API	Query your data model over HTTP — run queries (/v1/load) and read metadata (/v1/meta)	Cube API token (a JWT) sent directly in the Authorization header — no prefix
AI API	Stream conversations with Cube AI agents (/chat/stream-chat-state)	Cube API key with the Api-Key prefix
Platform API	Manage Cube — deployments, data models, reports, workbooks, users, policies, and more	Bearer prefix for REST and SCIM 2.0

The exact header for each is shown above. The Platform and SCIM schemes are detailed on the Authentication page; the Core Data and AI headers are also documented on their own reference pages.

Available endpoints

Each API family has its own base URL — copy the exact host from the Cube interface where noted. Only HTTPS is accepted, and every request must be authenticated (see Authentication).

Core Data API

Base URL — your deployment’s data API host (the /cubejs-api base path is configurable):

https://{deployment}.{region}.cubecloudapp.dev/cubejs-api

Endpoint	Path
JSON query	POST /v1/load
SQL query	POST /v1/cubesql
Metadata	GET /v1/meta

AI API

Base URL — your agent’s Chat API URL (copy it from Admin → Agents → Chat API URL):

https://ai.{cloudRegion}.cubecloud.dev/api/v1/public/{accountName}/agents/{agentId}

Endpoint	Path
Stream chat state	POST /chat/stream-chat-state

Platform API

Base URL — your tenant host:

https://{tenant}.cubecloud.dev

Endpoints live under three path prefixes on that host, all taking the same token:

Prefix	What it covers
/api/v1/…	Management of deployments, workspace content, users, policies, and embedding
/build/api/v1/…	Data model authoring — files, uploads, dev mode, and branches. Routed to the build workers that own a deployment’s data model.
/api/scim/v2/…	SCIM 2.0 user and group provisioning

Resources by entity:

Entity	Resource	Version

| Deployments | /api/v1/deployments | v1 | | Deployment Creation | /build/api/v1/deployments | v1 | | Environments | /api/v1/deployments/{deploymentId}/environments | v1 | | Env Variables | /api/v1/deployments/{deploymentId}/env-vars | v1 | | Regions | /api/v1/regions | v1 | | Data Model | /build/api/v1/deployments/{deploymentId} | v1 | | Data Model Uploads | /build/api/v1/deployments/{deploymentId}/data-model | v1 | | GitHub | /api/v1/github | v1 | | GitHub Connection | /build/api/v1/deployments/{deploymentId}/github/connect | v1 | | dbt Sync | /api/v1/deployments/{deploymentId}/dbt-sync | v1 | | Folders | /api/v1/deployments/{deploymentId}/folders | v1 | | Reports | /api/v1/deployments/{deploymentId}/reports | v1 | | Workbooks | /api/v1/deployments/{deploymentId}/workbooks | v1 | | Notifications | /api/v1/deployments/{deploymentId}/notifications | v1 | | Workspace | /api/v1/deployments/{deploymentId} | v1 | | Users Admin | /api/v1/users | v1 | | User Attributes | /api/v1/user-attributes | v1 | | User Attribute Values | /api/v1/user-attribute-values | v1 | | Tenant Settings | /api/v1/tenant/settings | v1 | | OAuth Integrations | /api/v1/oauth-integrations | v1 | | User OAuth Tokens | /api/v1/user-oauth-tokens | v1 | | OIDC Token Configs | /api/v1/oidc-token-configs | v1 | | App Theme | /api/v1/app-config | v1 | | Embed | /api/v1/embed | v1 | | Embed Tenants | /api/v1/embed-tenants | v1 | | Dashboard Embed Access | /api/v1/deployments/{deploymentId}/workbooks/{workbookId}/embed-access | v1 |

| Users (SCIM) | /scim/v2/Users | SCIM 2.0 | | Groups (SCIM) | /scim/v2/Groups | SCIM 2.0 |

Client libraries

Core Data API

Query the Core Data API from JavaScript or TypeScript with Cube’s JS client, @cubejs-client/core, which also ships React, Vue, and Angular bindings and a WebSocket transport for real-time updates. See the JavaScript SDK reference for full usage.

npm install @cubejs-client/core

Platform API

The recommended way to call the Platform API from JavaScript or TypeScript is the official client, @cube-dev/platform-client. It wraps the OpenAPI spec on this site with end-to-end types for every endpoint, request, and response, plus optional React Query bindings.

npm

npm install @cube-dev/platform-client

Create a client with your tenant’s base URL and an auth header (see Authentication), then call any endpoint through the fully-typed fetchClient:

import { createCubePlatformClient } from '@cube-dev/platform-client';

const client = createCubePlatformClient({
  baseUrl: 'https://<tenant>.cubecloud.dev',
  // Returned on every request — provide the Platform API auth header.
  getHeaders: () => ({ Authorization: `Bearer ${process.env.CUBE_API_KEY}` }),
});

const { data, error } = await client.fetchClient.GET('/api/v1/deployments/', {
  params: { query: { first: 50 } },
});

for (const deployment of data?.items ?? []) {
  console.log(deployment.id, deployment.name);
}

React Query bindings

The @cube-dev/platform-client/react-query entry point adds a provider and typed hooks built on @tanstack/react-query (a peer dependency alongside react):

import { createCubePlatformClient } from '@cube-dev/platform-client';
import {
  CubePlatformApiProvider,
  useCubePlatformApiQuery,
} from '@cube-dev/platform-client/react-query';

const client = createCubePlatformClient({ baseUrl, getHeaders });

function App() {
  return (
    <CubePlatformApiProvider client={client}>
      <Deployments />
    </CubePlatformApiProvider>
  );
}

function Deployments() {
  const { data } = useCubePlatformApiQuery('get', '/api/v1/deployments/');
  return <ul>{data?.items.map((d) => <li key={d.id}>{d.name}</li>)}</ul>;
}

Schema types are exported as PlatformApiSchemas (e.g. PlatformApiSchemas['Deployment']). See the package CHANGELOG for release notes and breaking changes.