Authorization header. There are no sessions, cookies, or OAuth flows to manage — every request is stateless and self-contained. As long as your API key is valid and included in the request, Vook will process it. If the key is missing or incorrect, the request is rejected immediately with a clear error response.
Getting Your API Key
You generate and manage your API keys from the Vook dashboard. Follow these steps to get your first key.Sign in to your dashboard
Go to app.vook.ai and sign in with your Vook credentials.
Open API Keys settings
Click on your account avatar or name in the top-right corner, then navigate to Settings → API Keys.
Generate a new key
Click Generate New Key, enter a descriptive name for the key (for example,
production-app or dev-local), and confirm. Your new API key will appear on screen.Using Your API Key
Pass your API key in theAuthorization header of every request using the Bearer scheme. The examples below show how to do this in the most common HTTP clients.
Replace
YOUR_API_KEY in every example with the actual key you generated from the Vook dashboard. Never hard-code keys directly in source files — use environment variables instead (see the security guidelines below).API Key Security
Keeping your API keys secure is your responsibility. Follow these best practices to protect your keys and limit the blast radius if one is ever exposed. Use environment variables Store your API key in an environment variable instead of hard-coding it in your source code. For example:.env files and any file that might contain secrets to your .gitignore. Treat a committed API key as compromised — revoke it immediately and rotate to a new one.
Rotate keys regularly
Even if a key hasn’t been exposed, it’s good practice to rotate API keys on a regular schedule. You can generate a new key from the dashboard and update your environment variables without any downtime.
Use separate keys per environment
Create a distinct API key for each environment (development, staging, production). This limits the impact of a compromised key and makes it easy to revoke access to a single environment without affecting others.
Authentication Errors
When a request fails due to an authentication problem, Vook returns a standard HTTP error status code along with a JSON error body. The table below describes the authentication-related error codes you may encounter.| Status Code | Name | Meaning |
|---|---|---|
401 Unauthorized | Missing or invalid API key | Your request did not include an Authorization header, the header was malformed, or the API key does not exist. Check that you are passing the header as Authorization: Bearer YOUR_API_KEY. |
403 Forbidden | Valid key, insufficient permissions | Your API key was recognized but does not have permission to access the requested resource. This can happen if the key was scoped to specific endpoints or if your account lacks access to a feature. |
If you continue to see
401 errors after double-checking your key, try generating a new key from the dashboard. It’s possible the original key was revoked or expired. Contact Vook support if the problem persists.