Skip to main content
Importing is how an asset that already exists on chain becomes usable inside your instance. Trusset does not deploy it, does not hold it, and does not become a party to it. What the import creates is a record: what the token is, which standard it follows, what your instance calls it, and what you publish about it. That record is what the rest of the platform reads. A Lending market can only be deployed against a token this instance has imported, and the trading venues resolve their instruments the same way.

​
Base Path

Every request authenticates with an instance API key in the X-API-Key header. See Authentication. An import belongs to the instance that made it, so two instances importing the same contract each hold their own record.

​
What can be imported

Detection reads the contract and decides which standard it follows. Seven are recognized. Detection stops at the first match, in that order. A contract that answers none of them is refused with UNSUPPORTED_TOKEN.
A token this instance issued through Trusset is detected as erc3643 and carries details.trussetStockToken: true with its isin. It cannot be imported: it already belongs to the instance and is listed in its own assets. Import Token refuses it with TOKEN_IS_OWN.

​
Import a token

1

Detect

Detect Token reads the contract and returns what it is, before anything is written. It also answers alreadyImported and isOwn, so a form is never filled in for a request that can only be refused.
2

Import

Import Token writes the record. You supply the assetType, which is your classification of the asset and is not read from the chain.
3

Describe

Update Profile publishes your overview of the instrument: description, issuer name, sector, website, AMM contract and reserve document. Every importer edits its own overview.
4

Publish the instrument record

Save Instrument publishes the identifiers, the legal terms and the offering documents that lenders read. Only the token’s controller publishes it. Your instance does so directly when one of its verified wallets is the token’s owner, an agent or an admin. Otherwise the controller signs the record and your platform submits it through the issuer-signed flow. Everything in it is an assertion, not a Trusset verification.
5

Keep it current

Refresh On-Chain State re-reads the contract and reports whether the stored framework still matches what the chain says.

​
Chain-read facts and issuer assertions stay apart

The record holds two kinds of thing and never merges them. name, symbol, decimals, framework, totalSupply and metadata come from the contract. They are re-read by Refresh On-Chain State and by nothing else. assetType, imageURI and everything under profile are yours. No endpoint verifies them, and anywhere they surface downstream they are marked as issuer-asserted. The instrument record carries that provenance per field: who asserted the value, on which on-chain authority, and the signature that approved it.

​
Response envelope

On failure, success is false, data is null, and error carries code and message. Always branch on success rather than on the HTTP status alone.
IMPORT_NOT_FOUND answers with 400, not 404. Branch on the code.

​
Limits

An instance holds at most 200 active imports. The 201st is refused with IMPORT_LIMIT_REACHED. Removing an import frees a slot. Writes on this surface are limited to 10 requests per minute, keyed by API key. List Imports and Get Import are limited to 100 per minute. Both sit inside the ceiling of 200 per minute that applies to every request made with an instance API key. See Rate Limits.