Error Handling

The GBiPayments API uses HTTP status codes to indicate the success or failure of the API requests. The section describes the summary of these codes and what they mean in our context.

Summary

• Codes in the 2XX range mean that the API request was processed successfully.

• Codes in the 4XX range mean that something was wrong with the data that you sent. For example, you might have missed some required parameters/headers, or you might be using the wrong API credentials.

• Codes in the 5XX range indicate an error in processing on our end

Common HTTP Codes

Code	Description
200	OK - Request was successful
202	Accepted - Request has been accepted and acknowledged. We will now go ahead to process the request and notify you of the status afterwards.
400	Bad Request - Malformed request or missing required parameters
401	Unauthorized - Missing required headers, wrong Public or Secret Key etc
403	Forbidden - You are trying to access a resource for which you don't have proper access rights.
404	Not Found - You are trying to access a resource that does not exist
422	Unprocessable Entity - You provided all the required parameters but they are not proper for the request
500	Internal Server Error - We had a glitch in our servers. Retry the request in a little while or contact support
503	Service Unavailable – We are temporarily offline for maintenance. Please try again later.