Errors
Notch Pay errors codes
The Notch Pay API is RESTful and, accordingly, employs conventional HTTP response codes to indicate the success or failure of requests. This section provides an overview of these codes and their meanings within our context.
Summary
- HTTP status codes in the 2XX range indicate that the API request was processed successfully.
- Codes in the 4XX range signify issues with the data sent in the request. This could include missing required parameters/headers or the use of incorrect API credentials.
- Codes in the 5XX range indicate an error in processing on our end.
Codes
Code | Description |
---|---|
200 | OK - Request was successful |
201 | Created - The request was successful, and a resource was created as a result |
202 | Accepted - Request has been accepted and acknowledged. We will now go ahead to process the request and notify you of the status afterwards. |
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 - Malformed request or missing required parameters |
429 | Too Many Requests - You have exceeded the number of requests allowed in a given time frame. |
500 | Internal Server Error - We had a glitch in our servers. Retry the request in a little while or contact support. Rarely happens. |
503 | Service Unavailable – We are temporarily offline for maintenance. Please try again later. Rarely happens. |
Responses
When engaging with the Notch Pay APIs, it's crucial to comprehend the format of the responses you'll receive. This understanding will enable you to interpret the responses accurately and handle them effectively within your application.
Webhooks
Webhooks are created to relay real-time status updates, like notifications of successful payments. In essence, they consist of URLs that Notch Pay calls to deliver the ID of an updated object. Upon receiving the call, you should retrieve the latest status and handle any changes accordingly.