# Retiring Tokens

**`POST /api/v1/contracts/retire/pools/{poolId}/retire`**

Submits a token retirement request against the specified pool. Accessible by Standard Registry and User roles.

**Authentication:** Bearer token required (`Authorization: Bearer <token>`)

**Permission:** `Permissions.CONTRACTS_RETIRE_REQUEST_CREATE`

***

## Request

### Path Parameters

| Parameter | Type   | Required | Description     |
| --------- | ------ | -------- | --------------- |
| `poolId`  | string | Yes      | Pool identifier |

### Request Body

```json
[
  {
    "token": "0.0.5000001",
    "count": 100,
    "serials": []
  }
]
```

The request body is an array of token retirement entries.

| Field     | Type   | Required | Description                                       |
| --------- | ------ | -------- | ------------------------------------------------- |
| `token`   | string | Yes      | Hedera token identifier to retire                 |
| `count`   | number | Yes      | Number of tokens to retire                        |
| `serials` | array  | No       | Specific serial numbers (for non-fungible tokens) |

***

## Response

### Success Response

**Status:** `200 OK`

```json
true
```

### Error Responses

| Status                      | Description                   |
| --------------------------- | ----------------------------- |
| `400 Bad Request`           | Request body must be an array |
| `401 Unauthorized`          | Missing or invalid token      |
| `403 Forbidden`             | Insufficient permissions      |
| `500 Internal Server Error` | Unexpected server failure     |


---

# Agent Instructions: 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:

```
GET https://guardian.hedera.com/docs/develop/guardian/tokens/retirement-contract/retirement-apis/retiring-tokens.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.