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.

All API requests require authentication via an API key passed in the X-API-Key header. Trusset uses two key systems depending on the API you are accessing.

​
Instance API Keys

Instance API keys authenticate requests to the core platform APIs (Customers, Tokenization, Trading, Lending, Custody). Each key is bound to a specific and grants access only to that instance’s data and services. The current key format is: 
trusset_{instanceRef}_{secret}
instanceRef is an 8-character alphanumeric identifier for your instance. secret is a 64-character hex string. A complete key is 81 characters long. Instance API keys are managed through the API Key Management dashboard or via the key management API. Keys support rotation with a configurable overlap period: when you rotate a key, the old key enters a PENDING_ROTATION state and remains valid for 7 days, giving you time to update all consumers without downtime. Each instance supports up to 10 active keys.
Endpoints protected by instance auth also enforce service-level access. If your instance does not have a required service enabled (e.g., tokenization), the request returns 403 with code SERVICE_NOT_ENABLED.

​
Error Responses

CodeErrorMeaning
401AUTH_REQUIREDNo X-API-Key header provided
401AUTH_FAILEDKey is malformed, not found, expired, or the instance is archived
403SERVICE_NOT_ENABLEDThe requested service is not activated for this instance
500AUTH_ERRORInternal authentication failure

​
MiCA Register API Keys

The MiCA Register API uses its own key system with the prefix trusset_mica_. These keys are free and provide access exclusively to the MiCA Register endpoints. Register at trusset.org/mica-register to generate your key. After registration you receive two credentials:
  • API Key (trusset_mica_...) - used in X-API-Key for data requests
  • Management Token - used in Authorization: Bearer ... for key management operations (rotating, revoking)
Store both credentials securely. They cannot be retrieved after initial generation.

​
Error Responses

CodeErrorMeaning
401UNAUTHORIZEDNo API key provided or key does not start with the expected prefix
401INVALID_KEYKey is malformed, revoked, or not found
500AUTH_ERRORInternal authentication failure

​
Making Requests

Both key types use the same header: 
curl -H "X-API-Key: your_key_here" \
  https://api.trusset.org/customers/api/manage