> This page is for Taurus PROTECT, version v3.52.
> 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.

# API Structure and Concepts

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](/protect-capital/reference).

![](/_fern-img/e8c72eaa76c1cf34902af599076e5314bbcb9c2d49fd47fc3718957f771ad5e8.webp)\


# 1. API Structure

We have structured the API endpoint in the following categories.

* [Wallets and Addresses](ref:whitelistservice_getwhitelistedaddresses): all things related to the creation and management of wallets and addresses;
* [Transfers and Staking](/protect-capital/v3.52/reference/requests/force-kill-bundle): all things related to basic crypto or asset transfers and staking;
* [Token Issuance and Asset Servicing](/protect-capital/v3.52/reference/requests-contracts/create-outgoing-call-request): all things related to tokenising assets, deploying smart contracts and interacting with said contracts;
* [Taurus Network](/protect-capital/v3.52/reference/taurus-network-sharing/get-shared-addresses): all endpoints related to Taurus-NETWORK;
* [Identity and Access Management](/protect-capital/v3.52/reference/visibility-groups/list): all things related to users, groups, and authentication (SSO);
* [Policy Engine](/protect-capital/v3.52/reference/governance-rules/get-rules): all things related to governance rules and policy orchestration;
* [System Administration](/protect-capital/v3.52/reference/steward/initialize-tenant): all things related to Taurus platform administration (prices, statistics, jobs, business rules,  etc.)
* [3rd Party Integrations](/protect-capital/v3.52/reference/scores/refresh-address): all things related to integration of third-parties such as exchanges, KYT scores, FIAT providers;
* [Airgap Cold HSM](/protect-capital/v3.52/reference/air-gap/submit-incoming): self-explanatory;
* [Webhooks](/protect-capital/v3.52/reference/webhook-calls/list): self-explanatory;

# 2. Important concepts

## Entities

It is recommended to first get familiar with the different concepts or [Definitions](doc:glossary) 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](/protect-capital/reference/authentication-1) chapter. To keep the code examples concise, they build on a proxy server introduced in the [HMAC authentication proxy](/protect-capital/reference/hmac-based-authentication#proxy-server-for-hmac-requests) 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](/protect-capital/v3.52/reference/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](/protect-capital/v3.52/reference/whitelisting) 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**
>
> **Note**
>
> This section requires both [authentication](/protect-capital/v3.52/reference/authentication-1) and creating [signatures](/protect-capital/v3.52/reference/signing-for-approval)!

## Creating Transactions

Taurus-PROTECT provides a variety of ways to create transactions safely. The [transactions](/protect-capital/v3.52/reference/transactions-1) 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**
>
> **Note**
>
> This section requires both [authentication](/protect-capital/v3.52/reference/authentication-1) and creating [signatures](/protect-capital/v3.52/reference/signing-for-approval)!