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

# Introduction

**Welcome to Taurus developers' guide.**\
Our developers' guide provides developers with the toolkit, APIs, examples to integrate with Taurus-PROTECT (custody platform) and Taurus-CAPITAL (issuance and tokenisation platform).\
Our developers' guide has been developed by developers for developers and should allow you to easily kickstart integration. More advanced concepts and architecture is described in our [User Guide](/user-guides/docs/introduction) (*password protected*). Feel free to have a look there where applicable.

![Taurus Protect overview grey.PNG](/_fern-img/37e00b2debe30bf95b75f50a1c751727592c9522d076a00916f537bc208fcf8f.webp)

# Entities

It is recommended to first get familiar with the different concepts or [Definitions](/protect-capital/v3.40/reference/entities) that can be managed via the APIs.

# Examples

For more detailed examples, please visit the [Develop and Integrate](/protect-capital/v3.40/docs/introduction-to-taurus-protect-api) section of our documentation.

# Core principles

## Authentication

Most of the interactions with the APIs of Taurus-PROTECT or Taurus-CAPITAL require to be authenticated and authorised.

In order to access the API, a valid API key is required. The API Key has the form of a **JWT token** that must be passed in the header to the HTTP request:

```http
Authorization: Bearer <JWT_Token>
```

For example:

```http
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6MTEsImV4dGVybmFsVXNlcklEIjoidGVhbTFAYmFuay5jb20iLCJ0ZW5hbnRJRCI6MSwiZmlyc3RuYW1lIjoiSm9obiIsImxhc3RuYW1lIjoiVDEiLCJyb2xlcyI6WyJyZXF1ZXN0Y3JlYXRvciIsInJlcXVlc3RhcHByb3ZlciIsInByaWNldXBkYXRlciJdLCJlbWFpbCI6InRlYW0xQGJhbmsuY29tIiwiZXhwIjoxNjE0NjA4MzgxLCJpYXQiOjE2MTQ2MDQ3ODF9.TKal8nrtkWobgsF3HPGS2THxND1_TF4ICjQFlHEIp0Q
```

### Integrity

In order to guarantee the integrity of addresses, the latter are signed, and their signature is verified by every component (in the backend, in the frontend):

* internal addresses, whose private keys are managed by Taurus-PROTECT, are signed by the HSM
* external addresses, whose private keys are **not** managed by Taurus-PROTECT, are approved and signed by selected users of Taurus-PROTECT before any possible usage.