Headers
The Basic Authentication header. Format: "Basic {base64(orgID:apiKey)}"
Path Parameters
The key of the ledger. Examples:
- "123e4567-e89b-12d3-a456-426614174000"
- "id:123e4567-e89b-12d3-a456-426614174000"
- "ref:ledger:customer_a"
Body
The unique identifier for the asset move to be updated. Either 'ref' or 'id' must be provided, but not both.
The new status for the asset move. Should be one of the valid AssetMoveStatus values.
An array of categories to associate with the asset move. These can be used for classification or reporting purposes.
Additional custom data to associate with the asset move. This can be any JSON-serializable object.
Response
The request has succeeded.
The unique reference of the asset move, set by you when creating the asset move
The representation of the source account Represents an account reference for asset moves. Used to specify source or destination accounts in asset movement operations. Exactly one of 'ref' or 'id' must be provided.
The represantation of the destination account Represents an account reference for asset moves. Used to specify source or destination accounts in asset movement operations. Exactly one of 'ref' or 'id' must be provided.
The reference of the asset
1
The amount of the asset to move
The status of the asset move Represents the current status of an asset move. Asset moves are transfers of assets between accounts and form the basis of transactions. Note: LOCKED and COMPLETED statuses affect account balances, while EXPECTED, DECLINED, and REFUNDED do not impact or release cap
EXPECTED
, LOCKED
, COMPLETED
, DECLINED
, REFUNDED
The type of the asset move
1
The created at timestamp
The updated at timestamp
the specific decline reason for the asset move in case the asset-move has been declined. This can be a system-defined reason such as INSUFFICIENT_FUNDS, or LIMIT_EXCEEDED, or it can be a custom defined type of so set during the transaction creation
The categories of the asset move
Additional, optional, metadata for the asset move