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

# Error Reference

> Common API error responses and how to resolve them

When an API request fails, the platform returns a structured error response with details about what went wrong. This section helps you diagnose and resolve common errors.

## Understanding error responses

API errors return a JSON response with the following structure:

```json theme={null}
{
  "type": "https://docs.narrative.io/reference/errors/...",
  "title": "Error Title",
  "status": 409,
  "detail": "Detailed explanation of what went wrong",
  "instance": "/api/endpoint",
  "logId": "unique-error-identifier"
}
```

| Field      | Description                                          |
| ---------- | ---------------------------------------------------- |
| `type`     | URL identifying the error type with resolution steps |
| `title`    | Brief error summary                                  |
| `status`   | HTTP status code                                     |
| `detail`   | Detailed explanation of the problem                  |
| `instance` | The API endpoint that produced the error             |
| `logId`    | Unique identifier for support requests               |

<Tip>
  When contacting support about an error, include the `logId` value to help quickly identify your specific issue.
</Tip>

## Common errors

<CardGroup cols={2}>
  <Card title="Access Rule, Table, or View Already Exists" icon="clone" href="/reference/errors/access-rule-name-conflict">
    Resolve HTTP 409 naming conflicts when creating access rules, datasets, or views
  </Card>

  <Card title="Dataset Schema Incompatible with Connector" icon="plug-circle-exclamation" href="/reference/errors/dataset-schema-connector-incompatible">
    Resolve HTTP 400 schema validation failures when connecting datasets to connectors
  </Card>
</CardGroup>

## General troubleshooting steps

1. **Read the error detail** — The `detail` field usually explains exactly what's wrong
2. **Check the status code** — Identifies the category of error (400 for validation, 409 for conflicts, etc.)
3. **Review your request** — Look for the specific element mentioned in the error
4. **Check the `type` URL** — Follow the link for detailed resolution steps