Error Response Format
Every Vaikora API error includes a code, message, HTTP status, and request_id for tracking. The consistent structure lets you parse and log errors reliably across your integration.
HTTP Status Codes and Common Errors
Vaikora uses standard HTTP status codes (4xx client errors, 5xx server errors) mapped to specific error codes like authentication failures, security policy violations, and rate limit hits. Know which codes signal retryable vs permanent failures.
Authentication and Security Errors
Authentication errors (invalid credentials, expired tokens) and security errors (blocked requests, policy violations, threat detection) require different handling. Some trigger immediate rejection; others log for audit and remediation.
Rate Limiting and Exponential Backoff
When rate limits trigger (429 status), Vaikora includes retry-after headers. Implement exponential backoff with jitter to handle throttling gracefully without overwhelming the gateway.