Start
Authenticate with your Veritas API key.
Each API key is scoped to a single workspace. If you manage multiple workspaces, create and use separate API keys for each one. Keys cannot access resources from another workspace.
Request header
http
x-api-key: sk_live_REPLACE_WITH_YOUR_KEYSend your key in the x-api-key header. Authorization: Bearer is not supported. Keep API keys in server-side environment variables and rotate a key immediately if it is exposed.
Authentication failures
| HTTP | Condition | Response |
|---|---|---|
| 401 | Missing key | { success: false, error: "API key is required" } |
| 403 | Unknown or inactive key | { success: false, error: "Invalid API key" } |
| 403 | Missing key permission | The response identifies the required permission. |
| 402 | Plan does not include feature | Upgrade or use a workspace with the required entitlement. |
Feature access
| Capability | Requirement |
|---|---|
| Single and universal verification | An active API key and available verification credits. |
| Batch verification | A plan and key with batch verification access. |
| Image verification | A plan and key with image verification access and image credits. |
| Commerce and automation | A plan and key with products, payment links, webhooks, or notifications enabled. |