Exchange Accounts

Taurus PROTECT provides the ability to interact with exchange accounts. Both withdraw and deposit is supported, allowing you to manage balances on exchanges directly from PROTECT or your integrated applications.

📘

In this article

In this article we will cover:

• Adding exchange accounts to PROTECT via API.
• Withdrawing and depositing to exchange accounts via API.

Prerequisites

• Transaction Governance rules that allow the currency and transfer amount.
• Address Whitelisting rules for the relevant currency.
• The WhitelistedAddressCreator role.
• Exchange must be added to your tenant (contact support). Note that you will require API keys for each exchange.

Adding an address from an exchange account

In order to interact with an external address on an exchange, you must first whitelist the address as an exchange address.

1. Look up the exchange account ID by calling the List Exchange Accounts endpoint.
2. Use the Create Whitelisted Address endpoint to create an exchange address and include the address you wish to whitelist. See the following body for example.

{
  "label": "Kraken ETH deposit",
  "address": "0x39c462...",
  "blockchain": "ETH",
  "addressType": "exchange",
  "exchangeAccountId": 42,
  "network": "mainnet"
}

3. Sign the approved request. See Signing for Approval.

Exchange account interactions: deposit and withdrawals

Using PROTECT, you can withdraw and deposit to/from exchange accounts using the /api/rest/v1/requests/outgoing and incoming endpoints respectively.

1. Look up the exchange account ID as you did in the steps above.
2. To transfer from PROTECT to the exchange, use the outgoing endpoint.
3. To transfer from the exchange to PROTECT use the incoming endpoint.

Example body:

{
  "amount": "1000000000000000000",
  "fromExchangeId": 1,
  "toAddressId": 123,
  "comment": "Receiving ETH from Binance"
}

4. Approve the request as normal (see signing for approval).

🚧

Important Considerations

Please note that there are several important things to note when it comes to exchange interactions:

• Valid API keys must be provided and invalidated keys will result in failed exchange interactions.
• A whitelisted address must be added for each blockchain and network combination. You cannot simply whitelist a single address for the whole exchange.