Disabling A Wallet Via A Change

Basic Description

This endpoint is used to disable an Wallet in Taurus-PROTECT. Disabling a wallet in Taurus-PROTECT means that you can no longer spend funds from a certain wallet. However, you can still receive funds to that wallet from blockchain transactions.

This endpoint would accept a POST request with a JSON payload containing the Change with the business rule that needs to be created in order to disable the wallet. The entity, action, and changes containing the rulewalletId, rulevalue and rulekey are the three required parameters that must be included within the JSON payload. Please take a closer look to the cURL example below in this page.

❗️

Disabling a wallet in Taurus-PROTECT

When an wallet is disabled in Taurus-PROTECT, it means that you can no longer spent the funds held in that wallet . However, the wallet can still receive funds from blockchain transactions.

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:

• Admin
• TPUser

To find out more about roles, please refer to the following page 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:

• rulewalletId: The ID of the wallet to be deactivated in Taurus-Protect.

📘

Preconditions

It is important to note that the selected wallet needs to be already created in Taurus-PROTECT. If the given rulewalletId does not exist, the request will eventually result in an error.

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.

export BASEURL=https://taurus-protect-instance.com
export APIToken=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6MSwiZXh0ZXJuYWxVc2VySUQiOiJ0ZWFtMUV4dGVybmFsVXNlcklEIiwidGVuYW50SUQiOjEsImNhcGl0YWxUZW5hbnRJRCI6MSwiZmlyc3RuYW1lIjoiSm9obiIsImxhc3RuYW1lIjoiRG9lIiwicm9sZXMiOlsidHB1c2VyIl0sImVtYWlsIjoidGVhbTFAYmFuay5jb20iLCJ1c2VybmFtZSI6InRlYW0xIiwiand0X3JlbmV3YWJsZV9hbW91bnQiOjAsImlzX3RvdHBfZW5hYmxlZCI6ZmFsc2UsImF1dGhfc3RhdHVzIjoiU1VDQ0VTUyIsImxhc3RfbG9naW4iOiIyMDIzLTAxLTAxVDAwOjAwOjAwLjE0OTc0NDIzMloiLCJsb2dnZWRfaW5fd2l0aF9zc28iOmZhbHNlLCJrZXkiOiIiLCJleHAiOjE2ODEyMTkyNzYsImlhdCI6MTY4MTIxNzQ3Nn0.K_85arIrigpkN1yHttCydpeT6oVg2c6PyQnuji907Og
curl --location "$BASEURL/api/rest/v1/changes" \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header "Authorization: Bearer $APIToken" \
--data '{
   "entity":"businessrule",
   "action":"create",
   "changes":{
      "rulekey":"coin_enabled",
      "rulevalue":"0",
      "rulewalletid":"12417"
   }
}
'

This piece of code sends a POST request to https://your-protect-instance.example.com/api/rest/v1/changes with the JSON string in the request body.

👍

Call Result

A successful response for the POST call to disable an address might look like this:

{
    "result": {
        "id": "4603"
    }
}

In this example, Taurus-PROTECT has created a Change to disable a wallet .Taurus-PROTECT responds with a JSON object containing the newly created Change ID. Please note that this Change then needs to be signed by an Admin for the address disabling process to be finalized.

Requirements for Future Use

For this particular endpoint, we do not have any storage requirements other than the Changeid that is included in the JSON Body Response.