Creating A Currency Rule Via A Change

Basic Description

This endpoint is used to update a currency or wallet rule in Taurus-PROTECT via a Change.
Wallet Rules and Currency Rules are automatically put in place by our system and users can take action to update these values with this endpoint.

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

Prerequisites

Required Roles

Certain API endpoints require that the user has a specific role in order to access them.

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. Every specific business rule has an entityId, in order to update the value, the action must be "update". rulevalue represents the value you would like to replace your current rule value with.

Call Example

You can find a basic example in cURL below. Here, we are changing the business rule for a currency, and have identified the entityId as "184". This value is the unique identifier of any singular business rule.

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",  
  "entityId": "184",  
  "action": "update",  
  "changes": {  
    "rulevalue": "20000"  
  }  
}'

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 create a change for a new user might look like this:

{
    "result": {
        "id": "4626"
    }
}

In this example, Taurus-PROTECT has provisionally created a new change for the admin quorum to review, and has assigned the relevant Change the unique ID of "4626".

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. This id will be used to Approve the Change with a different Admin in the next steps.

You can find the Swagger-generated page for this endpoint in the following link.