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

# Errors

> Standard error responses returned by the API.

# Error Handling

The API returns standard HTTP status codes and JSON error bodies.

## Error Response Format

```json theme={null}
{
  "statusCode": 400,
  "message": ["email must be an email"],
  "error": "Bad Request"
}
```

| Field        | Description                     |
| ------------ | ------------------------------- |
| `statusCode` | HTTP status code                |
| `message`    | Error message (string or array) |
| `error`      | Short error label               |

## Common Status Codes

| Code  | Meaning                                           |
| ----- | ------------------------------------------------- |
| `200` | OK — request succeeded                            |
| `201` | Created — resource created                        |
| `400` | Bad Request — validation failed                   |
| `401` | Unauthorized — missing or invalid token           |
| `403` | Forbidden — insufficient permissions              |
| `404` | Not Found — resource does not exist               |
| `429` | Too Many Requests — rate limit exceeded           |
| `500` | Internal Server Error — unexpected server failure |

## Validation Errors

The API uses `class-validator` with `ValidationPipe`. Invalid request bodies return a `400` with an array of messages describing each field error.

```json theme={null}
{
  "statusCode": 400,
  "message": [
    "name should not be empty",
    "email must be an email"
  ],
  "error": "Bad Request"
}
```