Error Handling
Last updated
All Zotlo API endpoints use a unified error response format. Successful requests return HTTP 200, while failed requests return HTTP 400 or HTTP 500.
{
"meta": {
"requestId": "app2.domain-REQ-5e73a811d5d",
"httpStatus": 400,
"errorMessage": "Subscriber profile not found.",
"errorCode": 400009
},
"result": []
}requestId
Unique request identifier generated by Zotlo.
httpStatus
HTTP status code (400,500).
errorMessage
Localized error message.
errorCode
Zotlo-specific error code (400008, 400009, etc.).
result
Empty or error-specific content.
All successful responses always return HTTP 200, even if business logic fails (e.g., subscription canceled).
Technical failures return HTTP 400 or HTTP 500.
Error messages respect the Language header you send.
Retry logic is recommended only for 500000 or network errors.
404001
Invalid endpoint
401002
Invalid AccessKey or AccessSecret
400008
Invalid subscriberId
400009
Subscriber profile not found
500000
Internal server error
Tip for Debugging
Save the requestId value, our support team can use it to locate the exact log for any API call.
Last updated

