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

# E020015

**Unauthorized**

HTTP status: `401`

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 identity of the caller could not be established, so the request was not processed.

## Likely causes

* The API key is missing or not valid.
* The calling IP address is not whitelisted for the API key.

## How to resolve it

* Send your API key in the `PRIVATE-TOKEN` header. See [API v3 Authentication](https://docs.i3d.net/game-hosting/overview/apiv3-authentication.md).
* Check the key's IP whitelisting and expiration date on the control panel.
* Note that most authentication failures are stopped before they reach the Dedicated Networks API and are answered with a plain JSON body such as `{"status":401,"error":"missing api key",...}` instead of this error. Treat any `401` the same way.

## Example response

```json
{
  "title": "Unauthorized",
  "status": 401,
  "detail": "identity could not be established",
  "code": "E020015",
  "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/e020015.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.
