> ## Documentation Index
> Fetch the complete documentation index at: https://docs.decisionly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Errors

> Understanding Decisionly API error responses

Decisionly uses conventional HTTP response codes to indicate the success or failure of an API request. Codes in the `2xx` range indicate success. Codes in the `4xx` range indicate an error that failed because the request was invalid (missing information, an attempt to file a chargeback after the deadline, etc). Codes in the `5xx` range indicate an error with Decisionly's servers (these are rare).

## HTTP Status Codes

<ResponseField name="200" type="OK">
  Everything worked as expected.
</ResponseField>

<ResponseField name="201" type="Created">
  A new resource was successfully created.
</ResponseField>

<ResponseField name="202" type="Accepted">
  The request was accepted for processing.
</ResponseField>

<ResponseField name="400" type="Bad Request">
  The request was unacceptable, often due to missing a required argument.
</ResponseField>

<ResponseField name="401" type="Unauthorized">
  Missing or invalid API key.
</ResponseField>

<ResponseField name="403" type="Forbidden">
  The API key doesn't have permissions to perform the request.
</ResponseField>

<ResponseField name="404" type="Not Found">
  The resource or endpoint doesn't exist.
</ResponseField>

<ResponseField name="429" type="Too Many Requests">
  Too many requests in a short period of time.
</ResponseField>

<ResponseField name="500" type="Internal Server Error">
  Something went wrong on Decisionly's end.
</ResponseField>