Trusset Protocol - Infrastructure for Asset Tokenization

The Trusset API provides programmatic access to tokenization infrastructure, custody operations, trading, lending, and the MiCA Register. All endpoints follow REST conventions and return JSON responses.

Base URL

https://api.trusset.org

Response format

Every response follows a consistent envelope:

{
  "success": true,
  "data": { ... },
  "metadata": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2025-01-15T10:30:00.000Z"
  }
}

Error responses include a machine-readable code and human-readable message:

{
  "success": false,
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "Search query too long (max 200 chars)"
  }
}

Available APIs

Customers

Customer records, linked wallets, on-chain identity verification, and claims backed by zk-STARK KYC proofs. Customer records require the customers service; identity, proofs, verification profiles and ID links require identity.

MiCA Register

Query the EU MiCA registry. Search licensed CASPs, ART issuers, EMT issuers, and non-compliant entities sourced from ESMA. Free access with a MiCA API key.

Tokenization

Import a tokenized asset issued elsewhere and describe it for your instance. Detect the token standard, record the asset, publish the instrument profile and its documents, and keep the chain-read facts current.

Trading

Order book trading across three products: tokenized stocks, imported ERC-3643 security tokens, and tokenized commodities. Manage books and custody setup, enforce price references, and place orders. Each product has its own settlement model, so start from its overview.

Lending

Lending markets collateralized by imported security tokens, ERC-20, ERC-1400 and ERC-3643 alike. Deploy freeze or custody markets, publish NAV pricing, set rate modes and loan terms, manage liquidity and loans, and run the operator-driven liquidation settlement workflow.

Asset Register

The pledge record a register provider enters against a token. Read every collateral lock a lending market has taken, with the holder, the pledgee, the amount, and the transaction that created it.

Vaults

Deposit into a bank-operated earning vault and redeem shares. Discover vaults, read positions and live share price, and drive deposits and redemptions.

HTTP status codes

The API uses standard HTTP status codes:

Code	Meaning
`200`	Request succeeded
`201`	Resource created
`400`	Invalid request parameters
`401`	Missing or invalid API key
`403`	Service not enabled or resource access denied
`404`	Resource not found
`409`	Resource already exists
`429`	Rate limit exceeded
`500`	Internal server error
`502`	Upstream service error
`503`	Service temporarily unavailable

Write operations

Endpoints that touch a contract (identity verification, token issuance, redemptions, freezes, force transfers, oracle syncs, market deployments, loans, liquidations) do not execute anything. They return an unsigned payload built against the target contract. You sign it with your registered wallet and broadcast it yourself. Trusset holds no private key and has no signer. Nothing moves on-chain without a signature you produced. A write response carries one of four shapes, depending on what the operation needs:

Shape	Returned when	Payload
`SIGN_TRANSACTION`	One transaction is enough	`transaction` (`to`, `data`) and `functionName`
`SIGN_TRANSACTIONS`	Several transactions must run in order	`steps`, each holding its own `transaction`, `functionName`, and a `description` where the reason is not obvious
`SIGN_TYPED_DATA`	The contract wants a signature, not a transaction	`typedData` (EIP-712 `domain`, `types`, `primaryType`, `message`) and `display`
`txData`	Stock tokenization writes	`txData` (`to`, `data`, `value`)

Multi-step responses are ordered and must be broadcast in sequence. Where a contract pulls tokens from you, the ERC-20 approval is the first step.

Read-only endpoints (balance queries, holder lookups, transfer compliance checks, status lookups, market metrics) return data directly and need no signature.

Confirm a transaction

Some endpoints record state once the transaction is mined. To record it, call the same endpoint a second time with the transaction hash in the body:

{ "txHash": "0x9f2c...a41b" }

Trusset then reads the receipt from the chain and checks that the transaction was mined, succeeded, targeted the expected contract, and called the expected function with the arguments you claimed. Only then does it write to the database and return the mined result, including values that exist only after execution such as loanId, liquidationId, auctionId, and positionId. State is derived from the receipt, never from the request body. A confirm call that fails verification changes nothing.

Code	HTTP	Meaning
`INVALID_TX`	`400`	`txHash` is not a well-formed 32-byte hash
`TX_REVERTED`	`400`	The transaction was mined but reverted
`TX_WRONG_TARGET`	`400`	The transaction was sent to a different contract than the endpoint expects
`TX_WRONG_FUNCTION`	`400`	The calldata does not decode against the expected ABI, or calls a different function
`TX_NOT_VERIFIED`	`400`	The transaction decoded correctly but acts on a different loan, auction, or liquidation
`TX_NOT_FOUND`	`404`	No receipt yet. The transaction is unmined, dropped, or on another network

TX_NOT_FOUND is the expected response when you confirm too early. Wait for one confirmation and retry, rather than treating it as a failure.

Authorisation errors

Writes are authorised against the wallets registered on the instance, and against the roles those wallets hold on your contracts.

Code	HTTP	Meaning
`RELAYER_NOT_CONFIGURED`	`400`	No verified wallet is registered on this instance
`SIGNER_NOT_AUTHORIZED`	`403`	The wallet is not an authorised signer on the market oracle. The oracle owner must call `setAuthorizedSigner`.
`ROUTER_OPERATOR_ROLE_MISSING`	`400`	The wallet does not hold `OPERATOR_ROLE` on the liquidation router. The error carries `calldata` that grants it.
`ROUTER_ADMIN_ROLE_MISSING`	`400`	The wallet does not hold `DEFAULT_ADMIN_ROLE` on the liquidation router.
`MISSING_ROLE`	`403`	The wallet does not hold the contract role this operation requires. The error names it in `requiredRole`.
`ONCHAIN_SETTLEMENT_UNAVAILABLE`	`409`	The operation settles on-chain but has no wallet in the loop to sign. Order books configured for `OFF_CHAIN` settlement are unaffected.

Overview

MiCA Register

Customers

Tokenization

Trading

Lending

Asset Register

Vaults

API Introduction

Base URL

Response format

Available APIs

Customers

MiCA Register

Tokenization

Trading

Lending

Asset Register

Vaults

HTTP status codes

Write operations

Confirm a transaction

Authorisation errors

​Base URL

​Response format

​Available APIs

Customers

MiCA Register

Tokenization

Trading

Lending

Asset Register

Vaults

​HTTP status codes

​Write operations

​Confirm a transaction

​Authorisation errors

Base URL

Response format

Available APIs

HTTP status codes

Write operations

Confirm a transaction

Authorisation errors