Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.trusset.org/llms.txt

Use this file to discover all available pages before exploring further.

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 lifecycle management, on-chain identity verification, transfer compliance checks, and KYC verification links. Requires an instance API key with the tokenization service enabled.

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.

Stock Tokenization

Deploy, issue, redeem, and manage ERC-3643 stock tokens. Includes holder queries, balance lookups, role management, compliance checks, and webhook integrations.

Stock Trading

On-chain and off-chain order book trading for tokenized stocks. Manage order books, submit limit and market orders, query trades and settlements, and check custody balances.

Stock Lending

Overcollateralized lending markets for tokenized securities. Manage lending pools, monitor positions and health factors, execute liquidations, configure oracle price feeds, and set up automated hooks.

​
HTTP Status Codes

The API uses standard HTTP status codes:
CodeMeaning
200Request succeeded
201Resource created
400Invalid request parameters
401Missing or invalid API key
403Service not enabled or resource access denied
404Resource not found
409Resource already exists
429Rate limit or transaction limit exceeded
500Internal server error
502Upstream service error (e.g. vault provider unreachable)
503Service temporarily unavailable

​
Relayer Errors

Endpoints that submit blockchain transactions (identity verification, token issuance, redemptions, freezes, force transfers, oracle syncs, liquidations, and similar write operations) require a configured relayer. The relayer is a per-instance wallet whose private key is fetched from your vault provider (Doppler or HashiCorp Vault) at transaction time. If the relayer is not set up or is unavailable, the API returns one of the following errors:
CodeHTTPMeaning
RELAYER_NOT_CONFIGURED400No relayer has been configured for this instance. Set one up in the dashboard under Wallets > Configure Relayer.
RELAYER_FROZEN403The relayer has been manually frozen. Unfreeze it in the dashboard to resume transactions.
RELAYER_LIMIT_EXCEEDED429The daily transaction limit has been reached. The limit resets at midnight UTC. You can increase it in the dashboard.
RELAYER_CONFIG_ERROR500The stored vault configuration could not be decrypted. Reconfigure the relayer in the dashboard.
RELAYER_VAULT_ERROR502The private key could not be fetched from your vault provider. Verify your vault credentials and connectivity.
RELAYER_KEY_MISMATCH500The key returned by your vault does not match the wallet address on file. Reconfigure the relayer.
Read-only endpoints (balance queries, holder lookups, transfer compliance checks, status lookups, market metrics) do not require a relayer and will work without one configured.
When useRelayer is set to false or omitted on write endpoints, the API returns unsigned transaction data (txData) that you can sign and submit client-side. This path does not require a relayer.