The following chapters describe common workflows that use a combination of Taurus-PROTECT API endpoints to accomplish specific operational objectives.

For a complete list of available endpoints and a description of the parameters please refer to our API reference.

1. API Structure

We have structured the API endpoint in the following categories.

• Wallets and Addresses: all things related to the creation and management of wallets and addresses;
• Transfers and Staking: all things related to basic crypto or asset transfers and staking;
• Token Issuance and Asset Servicing: all things related to tokenising assets, deploying smart contracts and interacting with said contracts;
• Taurus Network: all endpoints related to Taurus-NETWORK;
• Identity and Access Management: all things related to users, groups, and authentication (SSO);
• Policy Engine: all things related to governance rules and policy orchestration;
• System Administration: all things related to Taurus platform administration (prices, statistics, jobs, business rules, etc.)
• 3rd Party Integrations: all things related to integration of third-parties such as exchanges, KYT scores, FIAT providers;
• Airgap Cold HSM: self-explanatory;
• Webhooks: self-explanatory;

2. Important concepts

Entities

It is recommended to first get familiar with the different concepts or Definitions that can be managed via the APIs.

Authentication

All workflow examples assume that you have a good understanding of the authentication and authorization mechanisms covered in the Authentication chapter. To keep the code examples concise, they build on a proxy server introduced in the HMAC authentication proxy section.

Creating Signatures for Approvals

Many actions in Taurus-PROTECT—such as creating a transaction request, or initiating staking—are subject to governance rules that require digital signatures from designated operators in groups. The Signing for approval section provides detailed guidance on generating ECDSA-SHA256 signatures to approve such requests across the Taurus-PROTECT system.

Whitelisting Contracts and Addresses

To interact with external addresses or contracts on the blockchain they must first be Whitelisted within the system. Only after a whitelisting request has been approved can funds be sent to an external address or calls made to a smart contract.

📘

Note

This section requires both authentication and creating signatures!

Creating Transactions

Taurus-PROTECT provides a variety of ways to create transactions safely. The transactions section of this documentation section provides a step-by-step guide to a simple, versatile workflow that covers a wide range of use cases.

📘

Note

This section requires both authentication and creating signatures!