> For the complete documentation index, see [llms.txt](https://apidocs.intserv.se/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.intserv.se/api-endpoints/accesskeys-remove.md).

# /accesskeys/remove

<img src="/files/-M5VUbC0pXukjxeyjAz2" alt="" data-size="line"> **`https://api.intserv.se/v1/accesskeys/remove`**

Removes an access key.

> Authentication Type: Integration API Key

### :envelope\_with\_arrow: Request Body Parameters

| Field | Type         | Description                                                             |
| ----- | ------------ | ----------------------------------------------------------------------- |
| `id`  | string(uuid) | Identifier of the access key to remove.                                 |
| `key` | AccessKey    | Access key specification. Only used if the `id` field is not specified. |

### Responses

#### :white\_check\_mark: 204 No Content&#x20;

Indicates that the access key has been removed. No payload is included in the response.

### Models

#### AccessKey Model

| Field            | Type   | Description                                                                                            |
| ---------------- | ------ | ------------------------------------------------------------------------------------------------------ |
| `identification` | string | Identification number. Read the [Access Keys](/api-overview/access-keys.md) overview for more details. |
| `type`           | string | Type of access key. Can be either `proximity` or `code`.                                               |

### Examples

Remove an access key by id:

```
{
    "id": "8d5e391e-a8c1-4af4-b80a-3fb671235083"
}
```

Remove an access key by specification:

```
{
    "key":
    {
        "identification": "0x00499602d2",
        "type": "proximity"
    }
}
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://apidocs.intserv.se/api-endpoints/accesskeys-remove.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.