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 StatusDescriptionHandling
200Success
400Bad requestSpot the invalid parameters from the message and retry by entering valid details
401UnauthorizedRefresh session ID and try again
500Internal/server errorRetry later
504Time-outRetry 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 TagDescriptionData Type
correlationIdUnique correlation identity parameter for each response of invalid access tokenString
bankCodeUnique bank identification codeAlphanumeric
errorCodeCode representing the error encounteredString
errorMessageMessage explaining the details about the error encounteredString
timeStampDate and time of the errorDate

Error Codes

errorCodeerrorMessage
MW-001Account doesn't exists
MW-400Connectivity error
MW-401Invalid or expired access token
MW-403Request is Forbidden
MW-404Resource Not Found
MW-405Requested Method not allowed
MW-406Not acceptable
MW-415Unsupported Media Type
MW-429Too many requests received
MW-500Signature or Technical error
MW-503Service Unavailable
MW-504Gateway Timeout

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>