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

# E020018

**Contract required to remove**

HTTP status: `409`

Returned by: Dedicated Networks API, `DELETE /networks/{networkId}`, `DELETE /prefixes/{prefixId}`.

## What happened

Deleting networks and prefixes you created yourself requires a contract with i3D.net, and none covers it. Nothing was removed and no teardown was started.

## Likely causes

* Your account has no commercial agreement that covers self-service networking, for example because it lapsed after the resource was created.

## How to resolve it

* Contact the i3D.net sales team to arrange a contract. Once it exists, the same request succeeds.
* A teardown that was already accepted is never refused with this code: repeating that `DELETE` continues it.

## Not to be confused with

`E020017` is the same refusal for a create. This code is returned for deletes only, so a client that reacts to `E020017` does not silently start receiving it for a different operation.

## Example response

```json
{
  "title": "Contract required",
  "status": 409,
  "detail": "removing networks on this account requires a contract with i3D.net; contact i3D.net support to arrange one",
  "code": "E020018",
  "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/e020018.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.
