curl --request GET \
--url https://api.example.com/api/v1/wallet/history[
{
"effective_balance_sat": 123,
"exited_vtxos": [
"<string>"
],
"id": 1,
"input_vtxos": [
"<string>"
],
"intended_balance_sat": 123,
"offchain_fee_sat": 1,
"output_vtxos": [
"<string>"
],
"received_on": [
{
"amount_sat": 1,
"destination": {
"type": "ark",
"value": "<string>"
}
}
],
"sent_to": [
{
"amount_sat": 1,
"destination": {
"type": "ark",
"value": "<string>"
}
}
],
"status": "pending",
"subsystem": {
"kind": "<string>",
"name": "<string>"
},
"time": {
"created_at": "2023-11-07T05:31:56Z",
"updated_at": "2023-11-07T05:31:56Z",
"completed_at": "2023-11-07T05:31:56Z"
},
"metadata": {}
}
]Returns the full history of wallet movements ordered from newest to oldest. A movement represents any wallet operation that affects VTXOs—an arkoor send or receive, Lightning send or receive, board, offboard, or refresh. Each entry records which VTXOs were consumed and produced, the effective balance change (if any), fees paid, and the operation status.
curl --request GET \
--url https://api.example.com/api/v1/wallet/history[
{
"effective_balance_sat": 123,
"exited_vtxos": [
"<string>"
],
"id": 1,
"input_vtxos": [
"<string>"
],
"intended_balance_sat": 123,
"offchain_fee_sat": 1,
"output_vtxos": [
"<string>"
],
"received_on": [
{
"amount_sat": 1,
"destination": {
"type": "ark",
"value": "<string>"
}
}
],
"sent_to": [
{
"amount_sat": 1,
"destination": {
"type": "ark",
"value": "<string>"
}
}
],
"status": "pending",
"subsystem": {
"kind": "<string>",
"name": "<string>"
},
"time": {
"created_at": "2023-11-07T05:31:56Z",
"updated_at": "2023-11-07T05:31:56Z",
"completed_at": "2023-11-07T05:31:56Z"
},
"metadata": {}
}
]Returns the wallet history
How much the wallet balance actually changed by. Positive numbers indicate an increase and negative numbers indicate a decrease. This is often inclusive of applicable fees, and it should be the most accurate number.
A list of IDs for VTXOs that were marked for unilateral exit as a result of this movement. This could happen for many reasons, e.g. an unsuccessful lightning payment which can't be revoked but is about to expire. VTXOs listed here will result in a reduction of spendable balance due to the VTXOs being managed by the [bark::exit::Exit] system.
The internal ID of the movement.
x >= 0How much the movement was expected to increase or decrease the balance by. This is always an estimate and often discounts any applicable fees.
How much the movement cost the user in offchain fees. If there are applicable onchain fees they will not be included in this value but, depending on the subsystem, could be found in the metadata.
x >= 0A list of IDs for new VTXOs that were produced as a result of this movement. Often change VTXOs will be found here for outbound actions unless this was an inbound action.
Describes the means by which the wallet received funds in this movement. This could include BOLT11 invoices or other useful data.
Show child attributes
A list of external recipients that received funds from this movement.
Show child attributes
The status of the movement.
pending, successful, failed, canceled Contains information about the subsystem that created the movement as well as the purpose of the movement.
Show child attributes
Contains the times at which the movement was created, updated and completed.
Show child attributes
Miscellaneous metadata for the movement. This is JSON containing arbitrary information as defined by the subsystem that created the movement.
Show child attributes
Was this page helpful?