Authentication
SeeAPI uses API Keys to authenticate protected /v1 requests. Open API Keys in Developer Center, create a key, and securely store the complete value shown in the creation dialog. Use separate keys for each application or environment.
The API Base URL for your target environment, as shown in the code example below. Use the API address, not the Docs website URL.
A complete API Key, not the masked value displayed in the key list.
An optional Webhook Signing Secret if you receive callbacks
⚠️ The complete API Key is shown only once. Store it before closing the creation dialog. If you lose it, create a replacement key; the full value cannot be viewed or copied again.
Set a daily credit limit
In Developer Center, set the optional Daily credit limit when creating a key, or use Edit limit for an existing key. This caps the net credits that one key can consume during a UTC calendar day.
Example daily limit, in credits per UTC day:
50000Leave the limit blank to remove the key-level daily cap. This does not grant credits or bypass other account limits. Configure it in Developer Center, not in the POST /v1/generations request body.
Send the API Key
Send exactly one Authorization header using the Bearer scheme and your complete API Key. Keep a single space after Bearer; do not paste a masked value, extra quotation marks, or line breaks into the header.
Authorization: Bearer YOUR_API_KEYAfter setting the environment variables below, run this request from your server to check authentication and read your credit balance. It does not create a generation task.
curl --request GET "$SEEAPI_API_BASE_URL/v1/credits" \
--header "Authorization: Bearer $SEEAPI_API_KEY"Keep your API Key secure
Send requests over HTTPS from your server. Keep the key in a server-side environment variable or secrets manager, never in public client configuration. Never include it in:
Browser-side JavaScript
Mobile application packages
Public source-code repositories
URLs or query parameters
Application logs, analytics, monitoring events, screenshots, or support messages. Redact the Authorization header when sharing diagnostics.
Use environment variables
Configure your server-side shell with the API address below and replace YOUR_API_KEY with your complete key. The displayed Base URL follows the current environment configuration; use the correct API address when moving between environments. Keep real secrets out of committed files and shell history.
export SEEAPI_API_BASE_URL='https://api.seeapi.com'
export SEEAPI_API_KEY='YOUR_API_KEY'API Key and webhook secret
These credentials are not interchangeable. The API Key authenticates requests you send to SeeAPI. The Webhook Signing Secret verifies callbacks SeeAPI sends to your server. Never send the signing secret as a Bearer token. For webhook verification, use the signing secret with the original raw request body before parsing JSON.
Authentication errors
401 Unauthorized — Check that Authorization: Bearer YOUR_API_KEY contains the complete, active key for the intended environment. Missing, malformed, invalid, disabled, or revoked credentials cannot authenticate. Correct the credential before retrying.
403 Forbidden — The request is not allowed. Check the required permissions and the key's model or Endpoint access; a valid key does not grant access to every operation.
404 Not Found — Check the model and Endpoint IDs against the corresponding model documentation. For task or asset requests, verify the exact resource ID and target environment. A 404 alone does not mean the key is invalid.
Do not automatically retry authentication or permission failures. If a key is exposed, disable or delete it in Developer Center promptly, replace it, and update affected services. For a planned replacement, verify the new key before retiring the old one. Deletion cannot be undone. Continue with Getting Started, then choose a model from the Image Models or Video Models sections in the Docs sidebar.