# Delete an own second factor

> One of the own second factors goes - with a session only.

- Effect: Destructive - Removes something for good. Agents ask first.
- Idempotent: no
- Stability: beta
- REST: `POST https://api.manitu.de/v1/access/tfa/delete`
- Page: /reference/access/tfa/delete/

**Removes something for good. Agents name what will be lost and wait for an explicit yes; a program should ask the same.**

## REST

`POST https://api.manitu.de/v1/access/tfa/delete`

### Authentication

One of `X-API-Key`, `Authorization: Bearer …` - never more than one in a request.

### Request body

JSON; unknown fields are refused.

- `tfa_id` (integer | string, required) - The factor, from access/tfa/list. (pattern `"^[1-9][0-9]*$"`; minimum `1`)

### Response

In `data`; the rest of the body as on every call.

- `tfa_id` (integer, required)

### Statuses

- `200` Success.
- `400` The request does not match the declared input schema.
- `401` No credential was presented, or it was not recognised.
- `403` The credential is not permitted to use this operation.
- `500` The server failed. Nothing about the request was wrong. Whether a change took effect is not known - check before trying it again.
- `503` The channel this operation forwards through is unavailable.

### Example

```sh
curl -X POST 'https://api.manitu.de/v1/access/tfa/delete' \
  -H 'X-API-Key: $API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"tfa_id":12345}'
```

## Example result

```json
{
  "tfa_id": 12345
}
```