Dolva authenticates requests using HTTP Bearer tokens. Every request to a protected endpoint must include a valid token in the Authorization header. Requests without a token, or with an invalid token, are rejected with a 401 Unauthorized response.
Getting Your API Token
Sign up or log in at dolva.ai and navigate to your account dashboard to retrieve your API token. Treat your token like a password — never share it or commit it to source control.
Your API token grants full access to your Dolva account. Store it securely using environment variables or a secrets manager — never hard-code it in your application code.
Using Your Token
Include your token in the Authorization header of every API request using the Bearer scheme:
Authorization: Bearer dv-xxxxxxxx
Examples
curl -X POST https://api.dolva.ai/v1/analyze/emotion \
-H "Authorization: Bearer dv-xxxxxxxx" \
-F "audio=@recording.wav"
Using Environment Variables
Avoid hard-coding your token. Store it in an environment variable instead:
export DOLVA_API_TOKEN="your_token_here"
Authentication Errors
| HTTP Status | Meaning | What To Do |
|---|
401 Unauthorized | Missing or invalid token | Check that your token is correct and included in the Authorization header |
403 Forbidden | Token valid but lacks permission | Contact support if you believe this is an error |
The GET /health endpoint does not require authentication and can be used to verify network connectivity without a token.