Troubleshooting Guide
Last updated: Phase 8.5
Common Issues
"Invalid API key" (AUTH.INVALID_API_KEY, 401)
- Verify the
X-API-Keyheader is present and correctly formatted - Check the key hasn't been revoked in the Tenant Dashboard
- Ensure you're using the raw key (starts with
vx_), not the key ID - Keys are case-sensitive — copy-paste exactly
"Tenant is suspended" (TENANT.STATUS.SUSPENDED, 403)
- Your tenant has been suspended by an administrator
- Contact your ValidonX administrator to resolve the suspension
- All API calls will fail until the tenant is reactivated
"License not found" (LICENSE.NOT_FOUND, 404)
- Verify the license key is correct and belongs to your tenant
- License keys are case-sensitive
- The license may have been deleted — check the Tenant Dashboard
"Maximum activations reached" (ACTIVATION.LIMIT_EXCEEDED, 403)
- Your license has reached its activation limit
- Check
error.details.currentanderror.details.limitin the response - Deactivate unused instances via the Tenant Dashboard
- Contact your administrator to increase the limit
"Rate limit exceeded" (RATE_LIMIT.EXCEEDED, 429)
- You've exceeded 1,000 requests per hour
- Check the
Retry-Afterheader for when to retry - Implement caching for license validation (recommended: 5-15 min TTL)
- Use exponential backoff for retries
"Validation failed" (VALIDATION.FAILED, 422)
- Check required fields in the request body
- Verify field types (e.g.,
quantitymust be an integer >= 1) - Check
error.detailsfor field-specific validation messages
500 Internal Server Error
- Include
meta.request_idwhen contacting support - Retry after a short delay (these are typically transient)
- If persistent, check the ValidonX status page
Getting Help
When contacting support, always include:
- The
meta.request_idfrom the error response - The
error.codevalue - The HTTP status code
- The request method and path
- Timestamp of the error