Documentation Index
Fetch the complete documentation index at: https://docs.vibepeak.ai/llms.txt
Use this file to discover all available pages before exploring further.
API Keys
All API requests (except/health) require authentication using an API key. API keys are tied to your VibePeak account and grant access based on your subscription plan.
Getting an API Key
- Log in to your VibePeak Dashboard
- Navigate to Settings → API
- Click Create API Key
- Give your key a descriptive name (e.g., “Production”, “Development”)
- Copy and securely store your key
API Key Format
VibePeak API keys follow this format:vpk_live_- Prefix identifying it as a VibePeak live API keyaBcDeFgHiJkLmNoPqRsTuVwXyZ123456- Random unique identifier
Live vs. Test Keys
Every key carries a prefix that fixes its mode for the life of the key:| Prefix | Mode | Behavior |
|---|---|---|
vpk_live_ | Live | Charges credits and runs the real generation pipeline, returning your real video |
vpk_test_ | Test | A free sandbox — charges nothing and returns a watermarked sample video |
vpk_test_) lets you build and verify your integration end to end without spending credits. It exercises the identical request, validation, async lifecycle, and signed-webhook surface as a live key.
See Test Mode for the full sandbox model, the
test_scenario parameter, and the livemode response field.Using Your API Key
Include your API key in theAuthorization header of every request:
Example Request
Authentication Errors
| Error Code | HTTP Status | Description |
|---|---|---|
MISSING_API_KEY | 401 | No API key provided in the request |
INVALID_API_KEY | 401 | The API key is malformed or doesn’t exist |
API_KEY_REVOKED | 401 | The API key has been revoked |
API_KEY_EXPIRED | 401 | The API key has expired |
PLAN_REQUIRED | 403 | Your plan doesn’t include API access |
Example Error Response
Security Best Practices
Never expose keys in client-side code
Never expose keys in client-side code
API keys should only be used in server-side code. Never include them in:
- JavaScript running in the browser
- Mobile app code
- Public repositories
- Frontend environment variables
Use environment variables
Use environment variables
Store your API key in environment variables rather than hardcoding:
Rotate keys periodically
Rotate keys periodically
Rotate your API keys periodically and immediately if you suspect compromise.
You can create a new key and revoke the old one from your dashboard.
Use separate keys per environment
Use separate keys per environment
Create separate API keys for development and production.
This limits the impact if a key is compromised.
Managing API Keys
Viewing Keys
From your API settings, you can see:- Key name and creation date
- Key prefix (first 8 characters)
- Last used timestamp
- Revocation status
For security, the full API key is never shown after creation.
Revoking Keys
To revoke an API key:- Go to Settings → API
- Find the key you want to revoke
- Click the Revoke button
- Confirm the action
401 error.
Plan Requirements
API access requires a Plus, Pro, or Max plan.| Plan | API Access | Concurrent Tasks |
|---|---|---|
| Free | ❌ | - |
| Starter | ❌ | - |
| Plus | ✅ | 1 |
| Pro | ✅ | 3 |
| Max | ✅ | 5 |
Upgrade your plan
Get API access by upgrading to Plus or higher

