Skip to main content

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)

Check the Retry-After header for how long to wait.

Not Found Errors (404)

Server Errors (500, 503)

If you receive 500 errors consistently, please contact support@mavera.io

Handling Errors in Code

Retry Strategy

For transient errors (429, 500, 503), implement exponential backoff:

Debugging Tips

Include request ID, timestamp, and full error response in logs for debugging.
The param field tells you exactly which field caused validation errors.
Keys must start with mvra_live_ and be exactly as copied from the dashboard.
Isolate issues by testing the raw API with curl before debugging SDK code.

Request IDs

Some error responses include a request_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.
Log this value in your application when errors occur. Example:

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:
  1. Check our status page for outages
  2. Review the error message and code
  3. 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