Handle endpoint errors
Status Codes
200
OK
API request was successful. The request was successfully processed. If needed, consumers are expected to save the response payload and respond, then display a success message to their customers. Do note that for transactional flows with external systems, the request is processed, and the status object would return the applicable status to display information correctly to the users.
400
Bad request
Invalid request parameters The parameters passed are invalid. This means the request was not committed, and the partner is expected to validate the parameters and try again. These are generally caused by requests not following the API specs. In addition, transactional calls where limits are breached also return the same response. Consumers are expected to validate their request payload, and for transactional flow, display relevant messages to their customer that the transaction amount attempted is breaching the applicable limit as returned via API response
401
Unauthorized
Unauthorized access The authorization credentials required for the resource were not provided or were invalid
403
Forbidden
Forbidden access The resource you are trying to access is not allowed
404
Not Found
Resource not found The resource being accessed does not exist
201
Created
202
Accepted
500
Internal Server Error
The system experienced issues processing the request
502
Bad Gateway
Bad gateway error An invalid response was received while processing the operation on the resource
503
Service Unavailable
Third-party provider error An external partner/service failed while processing the request
504
Gateway Timeout
No response was received while processing the operation on the resource
429
Too Many Requests