KAKUNIN

Authentication

All Kakunin API requests authenticate via API keys validated at the edge.

API Keys

Kakunin uses bearer token authentication. All keys are validated in edge middleware before any route handler runs.

Authorization: Bearer kk_live_xxxxxxxxxxxxxxxxxxxx

Keys are scoped to a tenant. Every request is isolated — no cross-tenant data access is possible.

Obtaining a Key

API keys are issued from the Kakunin dashboard. Each key is:

  • Hashed with SHA-256 before storage — the plaintext is shown once at creation
  • Scoped to your tenant
  • Revocable at any time without affecting other keys

Request Headers

HeaderRequiredDescription
AuthorizationYesBearer <api_key>
Content-TypePOST/PATCHapplication/json

Errors

StatusMeaning
401Missing or invalid API key
403Key exists but lacks permission
429Rate limit exceeded

Rate Limiting

Requests are rate-limited per API key using Upstash Redis. Limits are enforced before any database write.

TierLimit
Starter100 req/min
Pro500 req/min
EnterpriseCustom

When rate-limited, the response includes:

{ "error": "Rate limit exceeded" }

with a 429 status and a Retry-After header.

On this page