Assets

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 is accepted. 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.

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.

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 id is the value transactions and inventory return as asset.uuid, and its codes are the values accepted as asset.code.
• Inventory accepts asset_id and asset_code filters that take those same values.