Authentication

Quickstart

curl https://api.reelsbuilder.ai/api/v1/usage \
  -H "Authorization: Bearer rb_your_api_key_here"

GET /api/v1/account/credits remains available as a compatibility alias. New integrations should use GET /api/v1/usage, which returns the prepaid API balance, pricing, and concurrency limits.

Get a key

Sign in and open Settings → API. Generate an API key in settings to create a live key. The full key is shown only once; copy it into your backend's secret manager. Newly created keys are stored as hashes, with a masked prefix shown in the dashboard.

The key button creates live keys. For a sandbox key, contact admin@reelsbuilder.ai or your ReelsBuilder contact. Sandbox generation returns fixtures without rendering or spending credits; see the sandbox limitations.

Header format

Send the key in the Authorization header using the Bearer scheme:

Authorization: Bearer rb_your_api_key_here

Send the complete key exactly as issued. The key is case-sensitive.

Key shape

• Prefix: All production keys start with rb_. Sandbox keys start with rb_test_ and return fixtures without charging live credits.
• Handling: Treat keys as opaque credentials. Do not truncate them or depend on a fixed length. Check meta.key_mode in the usage response to confirm the mode.

Examples by language

cURL

curl https://api.reelsbuilder.ai/api/v1/usage \
  -H "Authorization: Bearer $REELSBUILDER_API_KEY"

TypeScript (server-side fetch)

const response = await fetch(
  "https://api.reelsbuilder.ai/api/v1/usage",
  {
    headers: {
      Authorization: `Bearer ${process.env.REELSBUILDER_API_KEY}`,
    },
  },
);
if (!response.ok) throw new Error(`API request failed: ${response.status}`);
const data = await response.json();

Python (requests)

import os, requests

response = requests.get(
    "https://api.reelsbuilder.ai/api/v1/usage",
    headers={"Authorization": f"Bearer {os.environ['REELSBUILDER_API_KEY']}"},
    timeout=30,
)
response.raise_for_status()
data = response.json()

Rotation

In Settings → API, select Rotate Key to replace your live key. The old key stops working immediately, so update your application's secret and repeat the free usage check. Select Revoke Key to disable access without creating a replacement. Contact support to rotate or revoke a sandbox key.

Security checklist

• Store keys in environment variables, never in source control.
• Use a server-side proxy for browser clients; never call the API directly from frontend JavaScript with a live key.
• Treat the key like a password. Anyone with it can spend your credits and access your account's generated content.
• Confirm job results through authenticated polling before acting on a callback or publishing an asset.
• Rotate immediately if a key is leaked in logs, screenshots, or shared terminals.

Common authentication errors

• 401 AUTH_REQUIRED — No API key was supplied.
• 401 AUTH_INVALID_API_KEY — The key is invalid or has been revoked.
• 402 INSUFFICIENT_API_CREDITS — The account's API balance cannot cover the requested operation. This is a billing error; generating another key will not fund the account.

Next

Follow the quickstart to submit a video with an idempotency key and retrieve its result. See prepaid API billing before enabling paid calls.