Configure Assets

post

https://api.multi1.enterprise.taxbit.com/v1/assets

Creates up to 500 assets in a single request. Elements are processed independently: a failing element does not block or roll back the others, and the response returns one result per submitted element in the order submitted, each carrying its own status. The stablecoin/SEMP tag can only be set here, on creation, and cannot be changed by a later update.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Up to 500 assets to configure in a single request. Every element is reported individually in the response, in the order submitted. A failing element does not block or roll back the others, whether it fails a business rule (such as a duplicate name or code) or schema validation (such as a missing required field). Two elements in the same request that share a name or a code are treated the same way as a conflict with an already-configured asset: the first is created and the second is reported as an error. The request itself is rejected with a 400 only when the body is not an array of 1 to 500 elements.

Create Assets Request

name

string

required

length between 1 and 255

The name of the asset. Must be unique among your configured assets, compared without regard to capitalization. The capitalization supplied is the capitalization stored and returned. At most 255 characters.

type

string

enum

required

The class of asset. Transaction and inventory payloads publish the same values in title case (Crypto, Fiat, Precious Metal).

Allowed:

codes

array of strings

required

length ≥ 1

The codes that may be sent as asset.code on transactions for this asset. Each must be unique among your configured assets, compared without regard to capitalization, and at most 64 characters. The capitalization supplied is the capitalization stored and returned. At least one is required.

codes*

is_stablecoin_or_semp

boolean

Whether this asset is a stablecoin or SEMP (Specified Electronic Money Product). Taxbit derives the reporting jurisdictions for a tagged asset from a maintained list of codes rather than accepting them directly; see stablecoin_reporting_jurisdictions. Can only be set on creation, and true is accepted only when type is CRYPTO. On a response it is true for a tagged asset and omitted otherwise, the same way dtif_code and qualification_status are omitted when they do not apply.

Responses

Language

Credentials

Bearer

JWT

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200One result per submitted element, in the order submitted. Elements can fail individually while others succeed, so inspect each element's status field rather than the HTTP status code.

400The request body is not an array of 1 to 500 elements. Failures of individual elements do not use this status. They are reported per element in the 200 response.

401Unauthorized

403Forbidden

409A concurrent request configured an asset with the same name or code. Retrying the request reports the specific conflict on the affected element. Conflicts detected during normal processing do not use this status. They are reported per element in the 200 response.

429Too Many Requests