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

# API responses and errors

> Understand the HTTP status codes and error responses the Zapnito API returns, and how to handle them.

The Zapnito API uses standard HTTP status codes. The codes you're most likely to meet are:

| Status | Meaning |
| - | - |
| `200 OK` | The request succeeded. Some endpoints also return `200 OK` when there was nothing to change, such as adding a user who is already in a group. |
| `201 Created` | The request created a record. |
| `401 Unauthorized` | Your API token is missing, invalid, expired or badly formatted. See [authentication](/api/v1/authentication). |
| `403 Forbidden` | The account making the request doesn't have permission to do this. |
| `404 Not Found` | No record matches the ID, slug, UUID or email address in the request. |
| `409 Conflict` | The record you're creating already exists. |
| `422 Unprocessable Entity` | A required parameter is missing or invalid. The response lists the problems under `errors`, keyed by parameter name. |

## Error response formats

Error response formats aren't yet consistent across endpoints. Some return a JSON object with an `errors` key, and others return a plain text message. Check the endpoint page for the response you're handling.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.