Error codes
Responses and error-handling
HTTPS Error
Every request processed through the SingleView APIs will have a response among the following:
✔️ Successful ❌ Unsuccessful ⚠️ Error
HTTP Status | Description | Handling |
---|---|---|
200 | Success | |
400 | Bad request | Spot the invalid parameters from the message and retry by entering valid details |
401 | Unauthorized | Refresh session ID and try again |
500 | Internal/server error | Retry later |
504 | Time-out | Retry later |
Access Token Error
This error occurs when an invalid access token is provided in the requests. The following API response occurs in case of such error:
{
"correlationId": "2163bbf3-c6e1-4c0b-aac3-3b1b06552388",
"bankCode": "",
"errorCode": "MW-401",
"errorMessage": "UNAUTHORIZED",
"timeStamp": "2025-02-28T07:35:25.981+03:00"
}
Description
JSON Tag | Description | Data Type |
---|---|---|
correlationId | Unique correlation identity parameter for each response of invalid access token | String |
bankCode | Unique bank identification code | Alphanumeric |
errorCode | Code representing the error encountered | String |
errorMessage | Message explaining the details about the error encountered | String |
timeStamp | Date and time of the error | Date |
Error Codes
errorCode | Error Description | errorMessage |
---|---|---|
MW-400 | Connectivity error | |
MW-401 | Invalid or expired access token | UNAUTHORIZED |
MW-500 | Signature or Technical error | 401 |
Certificate Error
This error occurs when there is an issue with TLS handshake.
<html>
<head><title>400 Bad Request</title>
</head>
<body>
<center><h1>400 Bad Request</h1></center>
<hr><center>nginx</center></hr>
</body>
</html>
Updated about 20 hours ago