Error Response Format
All API errors follow a consistent format:HTTP Status Codes
Error Types
Authentication Errors (401)
Validation Errors (400)
Credit Errors (402)
Rate Limit Errors (429)
Retry-After header for how long to wait.
Not Found Errors (404)
Server Errors (500, 503)
Handling Errors in Code
Retry Strategy
For transient errors (429, 500, 503), implement exponential backoff:Debugging Tips
Log request and response details
Log request and response details
Include request ID, timestamp, and full error response in logs for debugging.
Check the param field
Check the param field
The
param field tells you exactly which field caused validation errors.Verify API key format
Verify API key format
Keys must start with
mvra_live_ and be exactly as copied from the dashboard.Test with curl first
Test with curl first
Isolate issues by testing the raw API with curl before debugging SDK code.
Request IDs
Some error responses include arequest_id (or similar) in the response headers or body. If present, include it when contacting support—it helps us locate the exact request in our logs.
Logging for Support
When reporting issues, provide structured information. Never log or share your full API key—only the prefix (e.g.mvra_live_abcd...).
For production error handling patterns, see Error Handling Patterns.
Getting Help
If you encounter persistent errors:- Check our status page for outages
- Review the error message and code
- Contact support@mavera.io with:
- Error message and code
- Request details (endpoint, parameters)
- Timestamp
- Request ID (if available)
- Your API key prefix (first 10 characters only)
Error Handling Patterns
Retries, backoff, user-facing messages
Authentication
Fix 401 errors
Rate Limits
Handle 429
Credits
Handle 402