Overview
The Assets endpoints let you configure, retrieve, update, and delete the assets your tenant uses within Taxbit's system. An asset represents a currency or instrument (crypto, fiat, or precious metal) that can appear on transactions.
Prerequisites
An asset must be configured before a transaction referencing its code can be ingested. Unknown codes are not created automatically: a transaction carrying a code that no configured asset claims is rejected, and the rejection identifies the unrecognized code. Configuring the asset and resubmitting the transaction resolves it, and a newly created asset is usable immediately.
Fiat currencies are configured for every tenant by default and do not need to be created. Any crypto asset or precious metal must be configured before transactions referencing it are sent. See Supported Fiat Currencies for the list of fiat codes.
Available Actions
- Configure Assets: Create up to 500 assets in a single request. Elements are processed independently, so a failing element does not block the others, and the response reports each element individually.
- List Assets: Return all assets configured for the tenant, with optional filtering by type.
- Look Up an Asset: Find a single asset by code or name using a full, case-insensitive match.
- Get an Asset: Fetch a single asset by its Taxbit-assigned UUID.
- Update an Asset: Edit the name or codes of an existing asset. The stablecoin/SEMP tag cannot be changed after creation.
- Delete an Asset: Remove an asset that is not referenced by any transaction.
Rate limits
Limits are applied per tenant, per endpoint, as a token bucket: the burst limit is the most requests accepted at once, and the refill rate is how quickly capacity returns.
| Endpoint | Refill rate | Burst limit |
|---|---|---|
| Configure Assets, Delete an Asset | 2 per second | 10 |
| Update an Asset | 10 per second | 50 |
| List Assets, Look Up an Asset, Get an Asset | 100 per second | 1000 |
Every response carries X-RateLimit-Limit and X-RateLimit-Remaining. A rejected request returns 429 with a Retry-After header stating how many seconds to wait.
Related
- Transaction Data Model describes where these assets are consumed. An asset's
idis the value transactions and inventory return asasset.uuid, and itscodesare the values accepted asasset.code. - Inventory accepts
asset_idandasset_codefilters that take those same values.
