Error Handling
All RMZ APIs use standard HTTP status codes and return structured JSON error responses.
Error responses from the Merchant API include an error: true field:
The Storefront API uses success: false:
The License API returns an error code string:
HTTP Status Codes
Validation Errors
When request validation fails (400 or 422), the response includes field-level errors:
Best Practices
Always check the HTTP status code first, then parse the response body for details.
- Check status codes — do not assume every response is successful
- Parse error messages — they contain actionable information
- Handle validation errors — iterate the
errors object to display field-specific messages
- Log errors — include the timestamp and request details for debugging
- Handle network errors — timeouts and connection failures are not JSON responses