{"document":{"Id":4,"PageName":"Errors","PageSlug":"Errors","MetaTitle":"Error Handling Documentation for APIs","MetaDescription":"Understand error codes and best practices for handling errors in API responses.\n","documentList":null},"documentdata":"
\n
\n

Errors<\/h3>\n

<p><span style="color: rgb(14, 16, 26); background-color: transparent;">Quick Moderate uses conventional HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 200 indicate success. Codes in the 400 indicate an error that failed given the information provided (e.g., a required parameter was omitted, a charge failed, etc.). Codes in the 500 indicate an error with Quick-Moderate's servers (these are rare). The above prescribed would help to identify whether the request of the API calls was working in which manner.<\/span><\/p><p><br><\/p><p>Certain 400 errors can be managed programmatically, such as when a card is declined. Each of these errors includes a specific error code that provides a brief explanation of the issue encountered.<\/p><\/p>\n\n <\/div>\n\n

\n
\n
\n HTTP Status Code Summary<\/span>\n <\/div>\n
\n
<p>Status CodeDescriptionExplanation200OKEverything worked as expected.400Bad RequestThe request was unacceptable, often due to missing a required parameter.401UnauthorizedNo valid App key provided.402Request FailedThe parameters were valid but the request failed.403ForbiddenThe App key doesn't have permissions to perform the request.404Not FoundThe requested resource doesn't exist.409ConflictThe request conflicts with another request (perhaps due to using the same idempotent key).429Too Many RequestsToo many requests hit the API too quickly. We recommend an exponential backoff of your requests.500, 502, 503, 504Server ErrorsSomething went wrong on Quick Moderate's end. (These are rare.) <\/p><\/div>\n <\/div>\n <\/div>\n \n <\/div>\n <\/div>\n "}