Common status codes
At Signzy, we strive to provide a seamless experience for developers using our APIs. When making requests to our APIs, we follow standard HTTP protocol and return appropriate HTTP status codes to indicate success or errors in the response. In the event of an error, we provide detailed information about the cause of the error encoded in the response as JSON, so that developers can quickly diagnose and resolve any issues.
Here is a list of HTTP status codes that you might encounter when using our APIs:
Code | Title | Description |
|---|---|---|
200 | OK | The request was successful. |
204 | No Content | Sucessfully Logged Out. |
304 | Not Modified | There was no new data to return. |
400 | Bad Request | The request was invalid or cannot be otherwise served. This may happen due to invalid Parameters passed.  This happens mostly when the input parameters are not in correct format and validation fails. |
401 | Authorization Required | Missing or incorrect authentication credentials. |
403 | Access Forbidden | The request is understood, but it has been refused or access is not allowed. An accompanying error message will explain why. This code is used when requests are being denied due to request limits.  Another Scenario that you'll encouter this error code in is when you are not allowed to hit a particular sub-component of the Signzy API. |
404 | Not Found | The URI requested is invalid or the resource requested is not available. |
409 | Conflict | This status also is given by Signzy APIs in case of an upstream being down, where the data to be downloaded requires Signzy to connect with upstream system, example PAN verification.  While processing the request, some dependency of the api didn't work as expected (unable to download/upload file, DB not responding, upstream not responding etc.), mostly due to a temporary issue. |
422 | Unprocessable Entity | Missing Inputs or the JSON body of a request is badly-formed. |
500 | Internal Server Error | Something is broken. This is usually a temporary error, for example in a high load situation or if an endpoint is temporarily having issues. |
502 | Bad Gateway | Signzy API you are hitting is down, or being upgraded. |
503 | Service Unavailable | The service is down for maintenance or is overloaded at the moment. |
504 | Gateway Timeout | The Signzy servers are up, but the request couldn’t be serviced within time due to some failure within the internal stack. |
Visit here for an exhaustive list of all the HTTP status codes.