Authentication

The Saiku Cloud API uses Bearer-token authentication. Every request to https://api.saiku.bi/me/* carries an API key that identifies your tenant.

Base URL

https://api.saiku.bi

Open the API keys page from the dashboard sidebar.
Click Create key.
Give the key a label (e.g. production-agent, staging-bot).
Copy the secret immediately — we only show it once. After this point the dashboard shows only the key ID + label.

Send the key in the Authorization header:

curl https://api.saiku.bi/me/tenant \
  -H "Authorization: Bearer sk_live_abc123…"

Successful response:

{
  "tenantId": "81e301f2-…",
  "tenantSlug": "acme",
  "tier": "team",
  "connectionName": "production-warehouse"
}

Rate limits are per-tenant, not per-key. The limits scale with your plan:

When you hit a limit, we return 429 Too Many Requests with a Retry-After header indicating when to retry.

Every error response is JSON:

{
  "error": "payment_required",
  "message": "This feature requires an active subscription or trial. Visit /billing to start your 14-day trial."
}

Common error codes:

Status	Code	Meaning
`401`	`unauthorized`	API key missing or invalid
`402`	`payment_required`	Tenant has no active subscription
`403`	`forbidden`	API key valid but lacks permission for this resource
`404`	`not_found`	Resource doesn’t exist (or isn’t visible to your tenant)
`429`	`rate_limited`	Per-minute or per-hour limit exceeded

On the API keys page, click Create key to mint a new one. Give it the same label as the key you’re rotating.
Update your agent / integration to use the new key.
Once you’ve confirmed the new key works in production, return to the API keys page and revoke the old one.

There’s no downtime — both keys are valid simultaneously until you revoke the old one.