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

# Errors

> Errors in the API follow the <a href="https://jsonapi.org/format/#error-objects" target="_blank">recommendation</a> from the JSON API spec.

An example error object returned in a response body looks like this:

```json theme={null}
{
  "errors": [
    {
      "status": "400",
      "title": "Bad Request",
      "detail": "The request could not be understood by the server due to malformed syntax.",
      "source": {
        "pointer": "/data/attributes/first-name"
      }
    }
  ]
}
```

Each error object includes a machine-readable `code` field, the stable identifier you match on programmatically, distinct from the human-readable `title` and `detail`.

Other potential error codes that may be returned are:

<CardGroup>
  <Card title="401 Unauthorized" icon="circle" iconType="solid" color="#dbdb00" />

  <Card title="403 Forbidden" icon="circle" iconType="solid" color="#FF0000" />

  <Card title="502 Bad Gateway" icon="circle" iconType="solid" color="#3B82F6" />
</CardGroup>

The `401 Unauthorized` and `403 Forbidden` errors above indicate a problem with your request, so fix the request before you send it again. A `502 Bad Gateway` error (code `bad_gateway`) is different: it means an upstream service the API depends on failed to respond. This is a transient condition, so retry the request after a short delay.

In all cases the response will be a JSON object with a single key `errors` which will be an array of error objects.

For more information, check out the [responses](https://jsonapi.org/format/#error-objects) in the API reference.