Authentication
Verytis uses Bearer API keys for authentication. Include your key in the Authorization header of every request.
Authorization Header
HTTP Header
Authorization: Bearer vt_live_...Example Request
cURL
curl "https://verytis.com/api/v1/discrepancies" \
-H "Authorization: Bearer vt_live_xxxxxxxxxxxxxxxxx"Key Format
Verytis API keys follow this format:
| Environment | Format |
|---|---|
| Live | vt_live_<secret> |
| Test | vt_test_<secret> |
Server-Side Usage Only
API keys are server-side secrets. Never expose them in client-side code.
Do not include Verytis API keys in:
- Browser JavaScript
- Mobile application bundles
- Public GitHub repositories
- Frontend environment variables
Specifically, do not prefix Verytis secrets with NEXT_PUBLIC_, VITE_, or any client-exposed environment variable prefix.
Error Responses
Authentication errors return HTTP 401:
JSON
{
"error": {
"code": "INVALID_API_KEY",
"message": "The provided API key is invalid.",
"request_id": "req_..."
}
}| Error Code | Description |
|---|---|
INVALID_API_KEY | The key is missing, malformed, or not recognized |
API_KEY_REVOKED | The key has been revoked |
API_KEY_EXPIRED | The key has expired |