> For the complete documentation index, see [llms.txt](https://docs.i3d.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.i3d.net/api/errors.md).

# Errors

Every error response of an i3D.net API that follows the shared API error model carries a stable, machine-readable `code`: `E` followed by six digits. This section has one page per code, stating what happened, the likely causes and how to resolve it.

A code carries no meaning in its digits: there are no ranges per product or per error type. Codes are stable: a code's meaning never changes. New codes may be added over time, so treat an unknown code as a generic failure of its HTTP status.

Each product section lists the codes its API can return and links here. For the structure of an error response, see the product's error handling page, for example [Dedicated Networks API error handling](/connectivity/dedicated-networks-api/error-handling.md).

| Code                              | Status | Title                                 |
| --------------------------------- | ------ | ------------------------------------- |
| [E020001](/api/errors/e020001.md) | 422    | Validation failure                    |
| [E020002](/api/errors/e020002.md) | 404    | Resource not found                    |
| [E020003](/api/errors/e020003.md) | 409    | Idempotency conflict                  |
| [E020004](/api/errors/e020004.md) | 409    | Delete blocked by IP addresses in use |
| [E020005](/api/errors/e020005.md) | 422    | Unknown fabric identifier             |
| [E020006](/api/errors/e020006.md) | 500    | Internal error                        |
| [E020007](/api/errors/e020007.md) | 409    | Network not ready                     |
| [E020013](/api/errors/e020013.md) | 400    | Unknown filter field                  |
| [E020014](/api/errors/e020014.md) | 409    | Delete blocked by IP addresses in use |
| [E020015](/api/errors/e020015.md) | 401    | Unauthorized                          |
| [E020016](/api/errors/e020016.md) | 409    | Quota exceeded                        |
| [E020017](/api/errors/e020017.md) | 409    | Contract required                     |
| [E020018](/api/errors/e020018.md) | 409    | Contract required to remove           |
| [E020019](/api/errors/e020019.md) | 409    | Resource is managed by i3D.net        |
| [E020023](/api/errors/e020023.md) | 405    | Method not allowed                    |
| [E020024](/api/errors/e020024.md) | 409    | Operation pending                     |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.i3d.net/api/errors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.