Authentication

All Buuk API endpoints require HTTPS. Authenticated routes expect a Bearer token in the Authorization header unless noted otherwise in the reference.

Bearer tokens

Create tokens with POST /auth/token. Each token is scoped to a single workspace and inherits the permissions of the user who created it.

Authorization: Bearer buuk_live_abc123

Token lifecycle

• Tokens expire after 24 hours — request a new one before expiry in long-running jobs
• Revoke compromised tokens immediately from Dashboard → Settings → API
• Use separate tokens per environment (sandbox vs production)

Error responses

Authentication failures return 401 Unauthorized with a JSON body:

{
  "error": "invalid_credentials",
  "message": "Email or password is incorrect."
}

SDK example

Official SDKs attach the bearer token automatically once configured:

import { Buuk } from "@buuk/sdk";

const client = new Buuk({ token: process.env.BUUK_API_TOKEN });
const { data } = await client.articles.list({ status: "published" });