Use this endpoint to create the Asset that will be used with the transactions. You can create multiple Assets. However, the Assets must be created one at a time, with each Asset requiring specific decimal place settings and other individual parameters to be defined during the creation process.
The authorization token. This header is required if your environment has the Access Manager enabled.
The type of media of the resource. Must be application/json.
A unique identifier used to trace and track each request.
The unique identifier of the Organization associated with the Ledger.
The unique identifier of the associated Ledger.
The name of the Asset, which must be unique.
256The type of Asset.
currency, crypto, commodity, others The code used to refer to the Asset, according to its type. Important: It's not possible to create assets with the same type and code. Also, if the Asset is a currency (type = currency), the code must follow the ISO 4217 values.
An object containing information about the status. Important: If not provided, the default status will be 'ACTIVE'.
An object containing key-value pairs to add as metadata, where the field name is the key and the field value is the value. For example, to add a Cost Center, use 'costCenter': 'BR_11101997'.
Indicates that the request was successful and the response contains the expected data.
The unique identifier of the Asset.
The unique identifier of the Organization.
The unique identifier of the Ledger.
The name of the Asset.
256The type of Asset.
currency, crypto, commodity, others The code used to refer to the Asset.
An object containing key-value pairs to add as metadata, where the field name is the key and the field value is the value. For example, to add a Cost Center, use 'costCenter': 'BR_11101997'.
Timestamp of creation (UTC).
Timestamp of last update (UTC).
Timestamp of soft deletion, if applicable (UTC).