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

# Errors Overview

> Vault API error format and where to find status codes and common errors.

Vault returns errors as JSON with `success: false` and a `message` field. Use the HTTP status code and message to decide whether to retry, fix the request, or prompt the user.

## Response format

```json theme={null}
{
  "success": false,
  "message": "Human-readable error message",
  "data": null
}
```

## Reference

| Page | Content |
| - | - |
| [HTTP status codes](/api-reference/vault/status-codes) | All status codes and typical causes |
| [Common errors](/api-reference/vault/common-errors) | Frequent messages and how to fix them |

## Quick reference

| Code | Meaning |
| - | - |
| 400 | Bad Request — fix input |
| 401 | Unauthorized — check API key or JWT |
| 403 | Forbidden — permissions or MFA |
| 404 | Not Found — resource doesn't exist |
| 409 | Conflict — duplicate or state conflict |
| 429 | Too Many Requests — back off; use `retry_after_seconds` if present |
| 5xx | Server/upstream error — retry with backoff |


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