> 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/e020001.md).

# E020001

**Validation failure**

HTTP status: `422`

Returned by: Dedicated Networks API, `DELETE /networks/{networkId}`, `DELETE /prefixes/{prefixId}`, `GET /fabrics`, `GET /ip-addresses/{ipId}`, `GET /networks/{networkId}/ip-addresses`, `GET /networks/{networkId}/operation`, `GET /networks/{networkId}`, `GET /networks`, `GET /prefixes/{prefixId}/ip-addresses/{ipId}`, `GET /prefixes/{prefixId}/ip-addresses`, `GET /prefixes/{prefixId}/operation`, `GET /prefixes/{prefixId}`, `GET /prefixes`, `GET /usage`, `PUT /networks/{networkId}`, `PUT /prefixes/{prefixId}`.

## What happened

The request was parsed, but a field or a query value is not acceptable. Nothing was created or changed. The request can never succeed as written.

## Likely causes

* A required field is missing, for example `connectivity` or `fabric` on a network create, or `networkId`, `family` or `size` on a prefix create.
* A public network was created without `addressing.prefixes`. There is no default public prefix.
* `connectivity.type` is `public` while `addressing.source` is `none`, or `addressing.source` is `none` together with a non-empty `addressing.prefixes`.
* `addressing.source` is `customer`. Only `provider` and `none` are supported.
* `size` asks for a block larger than a /24, or a private `cidr` has a mask outside /24-/29 (IPv4) or /48-/64 (IPv6).
* A `cidr` is given on a public network or on a prefix create (`PUT /prefixes/{prefixId}`). i3D.net selects those subnets; a `cidr` is accepted only on a private network create.
* A `cidr` is given together with `family` or `size`, is empty, is not a network address, is outside the private ranges (`10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fd00::/8`), or overlaps another prefix of the same request.
* `retention` is `ephemeral`. Resources you create are always persistent.
* `contractId` is missing on a persistent resource, has the wrong format, or was supplied where it must be omitted (`addressing.source: none`).
* `name` is empty after trimming or longer than 100 characters.
* On a prefix create, `networkId` does not name a network on your account. A network is never created as a side effect.
* A UUID in the request path (`networkId`, `prefixId` or `ipId`) is not a well-formed UUID. The lookup is never attempted; a well-formed UUID that names nothing is a `404` instead.
* On a listing, the `cursor` was not issued for this listing, `filters[fabric][eq]` and `filters[metro][eq]` were combined, or `filters[resourceType][eq]` names an unknown resource type.

## How to resolve it

* Read `detail`: it names the field or value and, where there is one, the accepted alternative.
* Correct the request body or query and send it again. For a create, keep the same UUID if nothing else changed; otherwise use a new one.
* For a prefix create, create the network first and wait until it is `active`.

## Example response

```json
{
  "title": "Validation failure",
  "status": 422,
  "detail": "a public network requires explicit addressing.prefixes[] (family and size) - there is no default public prefix",
  "code": "E020001",
  "traceId": "0af7651916cd43dd8448eb211c80319c"
}
```


---

# 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/e020001.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.
