> This page is for Taurus PROTECT, version v3.38.
> For other versions, use one of these documentation indexes:
> - v3.58 (default): https://taurushq.ferndocs.com/protect-capital/v3.58/llms.txt
> - v3.56: https://taurushq.ferndocs.com/protect-capital/v3.56/llms.txt
> - v3.54: https://taurushq.ferndocs.com/protect-capital/v3.54/llms.txt
> - v3.52: https://taurushq.ferndocs.com/protect-capital/v3.52/llms.txt
> - v3.50: https://taurushq.ferndocs.com/protect-capital/v3.50/llms.txt
> - v3.48: https://taurushq.ferndocs.com/protect-capital/v3.48/llms.txt
> - v3.46: https://taurushq.ferndocs.com/protect-capital/v3.46/llms.txt
> - v3.44: https://taurushq.ferndocs.com/protect-capital/v3.44/llms.txt
> - v3.42: https://taurushq.ferndocs.com/protect-capital/v3.42/llms.txt
> - v3.40: https://taurushq.ferndocs.com/protect-capital/v3.40/llms.txt
> - v3.38: https://taurushq.ferndocs.com/protect-capital/v3.38/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://taurushq.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://taurushq.ferndocs.com/_mcp/server.

# Creating A Dot Unstaking Request

## Basic Description

This endpoint is used to create an Unstaking Request in Taurus-PROTECT in the Polkadot Network. This will unbond the selected amount and the unbonded funds will then be locked for 28 days. Once this time period has passed, the funds can be claimed with a DOT WithdrawUnbonded request.\
To understand what Staking is, please refer to the following [page](/user-guides/docs/staking) in the Taurus User Guides.

This endpoint would accept a POST Request with a JSON payload containing the Unstaking Request details.

The `amount ` and   `fromAddressId` are the only required parameters that must be included within the JSON payload.

> **Warning**
>
> **Staking Amount for DOT**
>
> It is important to note that in the Polkadot Network, **you are allowed to select the amount you want to stake**.

## Prerequisites

### Required Roles

Certain API endpoints require that the user has a specific role in order to access them. Roles are used to restrict access to certain functionality within the system and ensure that only authorized users are able to perform specific actions.

Here is the list of required Roles for this particular endpoint:

* RequestCreator
* TPUser

To find out more about roles, please refer to the following [page](/user-guides/docs/users-1#creating-a-new-user) in the Taurus User Guides.

### Required Input Parameters

Certain API endpoints require specific input parameters. Here is the list of Required Input Parameters for this particular endpoint:

* **fromAddressId** : the originating Address
* **amount** : the amount you would like to unstake

> **Note**
>
> **Preconditions**
>
> It is important to note that the selected Addresses needs to pre-exist and be active in the system. In addition, the originating Address should have already been used for Staking, otherwise the Unstaking Request will fail.

## Call Example

You can find a basic example in cURL below.\
Please note that you will need to update the `BASEURL` and the `APITOKEN` for the command to function.\
In this example, Taurus-PROTECT has created a new Untaking Request for Address 485965 with 1 DOT as the specified amount and has assigned it a unique ID of 4268651.

**`cURL`**

```curl cURL
export BASEURL=https://taurus-protect-instance.com
export APIToken=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6MSwiZXh0ZXJuYWxVc2VySUQiOiJ0ZWFtMUV4dGVybmFsVXNlcklEIiwidGVuYW50SUQiOjEsImNhcGl0YWxUZW5hbnRJRCI6MSwiZmlyc3RuYW1lIjoiSm9obiIsImxhc3RuYW1lIjoiRG9lIiwicm9sZXMiOlsidHB1c2VyIl0sImVtYWlsIjoidGVhbTFAYmFuay5jb20iLCJ1c2VybmFtZSI6InRlYW0xIiwiand0X3JlbmV3YWJsZV9hbW91bnQiOjAsImlzX3RvdHBfZW5hYmxlZCI6ZmFsc2UsImF1dGhfc3RhdHVzIjoiU1VDQ0VTUyIsImxhc3RfbG9naW4iOiIyMDIzLTAxLTAxVDAwOjAwOjAwLjE0OTc0NDIzMloiLCJsb2dnZWRfaW5fd2l0aF9zc28iOmZhbHNlLCJrZXkiOiIiLCJleHAiOjE2ODEyMTkyNzYsImlhdCI6MTY4MTIxNzQ3Nn0.K_85arIrigpkN1yHttCydpeT6oVg2c6PyQnuji907Og
curl --location "$BASEURL/api/rest/v1/requests/outgoing/ada/undelegate" \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header "Authorization: Bearer $APIToken" \
--data '{
    "amount": "10000000000",
    "fromAddressId": "485965"
}'
```

This piece of code sends a POST request to  [ https://your-protect-instance.example.com/api/rest/v1/requests/outgoing/dot/unbond](https://your-protect-instance.example.com/api/rest/v1/requests/outgoing/dot/unbond) with the JSON string in the request body.

> **Tip**
>
> **Call Result**
>
> A successful response for the POST call to create an Unstaking Request for DOT might look like this:

```json
{
    "result": {
        "approvers": {
            "parallel": [
                {
                    "sequential": [
                        {
                            "externalGroupID": "team1",
                            "minimumSignatures": 1
                        }
                    ]
                }
            ]
        },
        "currency": "DOT",
        "currencyInfo": {
            "blockchain": "DOT",
            "coinTypeIndex": "354",
            "decimals": "10",
            "displayName": "Polkadot - DOT",
            "enabled": true,
            "hasStaking": true,
            "id": "cadc2268107de6d9749ca1d1a2f8df20f7cea5263a5cf3fb852395be08947a13",
            "isAccountBased": true,
            "name": "Polkadot",
            "network": "mainnet",
            "symbol": "DOT",
            "type": "native"
        },
        "envelope": "Cgc0MjY4NjUxELvw7fy65suuFxgOKoIGCCMSUAoBABJLCis0ODU5NjU6ZTAzOTAyMWItZDYwMy00YjM4LTgyZDQtNDZhMzQ0OTkzOGZmEhNtLzQ0Jy8zNTQnLzMnLzAnLzMnMgEAYgQJUvKYIhcKCnJlcXVlc3RfaWQQARoHNDI2ODY1MSIZCglydWxlc19rZXkQARoKRE9UX1VuYm9uZCIRCghjdXJyZW5jeRABGgNET1QiIQoNY3VycmVuY3lfbmFtZRABGg5Qb2xrYWRvdCAtIERPVCJRCgtjdXJyZW5jeV9pZBABGkBjYWRjMjI2ODEwN2RlNmQ5NzQ5Y2ExZDFhMmY4ZGYyMGY3Y2VhNTI2M2E1Y2YzZmI4NTIzOTViZTA4OTQ3YTEzIhQKB25ldHdvcmsQARoHbWFpbm5ldCJ6CgZzb3VyY2UQBBpmCAESYgjN1B0SMDE2UngxRmVXb24zdmpyeGNmTnBCMXFvWmU4VlYyeGh4eWdONk1VYmVQY3I5ckdqaBoVTm9zdHJvIG1haW4gYWRkcmVzcyAyIhNtLzQ0Jy8zNTQnLzMnLzAnLzMnIgZzb3VyY2UiogEKBmFtb3VudBAKGo0BCgEAEgYwLjAwMDAaETQuODM4MjgyNDAwMDAwMDAxIAoqA0RPVDIDQ0hGOmEKHXZhbGlkYXRvci1jb3JlQHRhdXJ1c2dyb3VwLmNoEkAAXCiwiQ0l8ndzQj2Mm9MepBodnrR5pwFFTsVp3dJJc0NQwLBXjSA+2aL5jFEm7YFsiMZG6mT55HF/sG+tCxW8IgZhbW91bnQiHQoRdG90YWxfZmlhdF9hbW91bnQQARoGMC4wMDAwIhYKCmZlZV9saW1pdHMQAxoGCgQJUvKYIh8KEXZhbGlkX3VudGlsX2Jsb2NrEAIaCAAAAAAA64vXIkIKD3RyYW5zYWN0aW9uX2lkcxAGGi0KKzQ4NTk2NTplMDM5MDIxYi1kNjAzLTRiMzgtODJkNC00NmEzNDQ5OTM4ZmYiHAoRaXNfY2FuY2VsX3JlcXVlc3QQARoFZmFsc2U6B21haW5uZXQ=",
        "id": "4268651",
        "rule": "rule = [source: any, amount: any], approvals = ['team1': 1 sig]",
        "status": "CREATED",
        "tenantId": "1",
        "trails": [
            {
                "action": "created",
                "externalUserId": "team1@bank.com",
                "requestStatus": "CREATED",
                "userId": "11"
            },
            {
                "action": "approvers_assigned",
                "comment": "rule = [source: any, amount: any], approvals = ['team1': 1 sig]",
                "externalUserId": "validator-core@taurusgroup.ch",
                "requestStatus": "CREATED",
                "userId": "1"
            }
        ],
        "type": "dot_unbond"
    }
}
```

Taurus-PROTECT responds with a JSON object containing the Unstaking Request details, including the Request `status` and the newly assigned Request`id`.

## Requirements for Future Use

For this particular endpoint, we need to store the Request`id` as it will be required in the next step where we will sign the Unstaking Request.

You can find the Swagger-generated page for this endpoint in the following [link](/protect-capital/v3.38/reference/requests-dot/create-outgoing-dot-unbond-request).