Approve Transaction
In this endpoint, enter the exact same values that were used when creating the transaction (for example, max_fees must be the exact same values).
You can retrieve transactions "pending approval" with GET /transactions?status=PENDING_APPROVAL.
However, you should NOT trust those values and you should implement your own source of trust.
If you've set up your API Key when initializing your LAM, you'll need to include it as a header along with the api user header. For more details, see step 5 of the get started documentation.
(required) Username of a registered API User
The transaction's ID.
The account's name.
The amount to be sent, in the currency's lowest unit. For Smart Contract interaction, use "0" instead of null
nullPattern: ^[0-9]*(\.[0-9]+)?$coin specific data
nullThe transaction's max fees, in the currency's lowest unit.
nullPattern: ^[0-9]*(\.[0-9]+)?$The recipient's address.
The approved transaction
10the transaction amount, in base units
nullExample: 1432199Pattern: ^[0-9]*(\.[0-9]+)?$nullExample: 2020-12-11T12:56:35.370946+00:00nullExample: {"fees_per_byte":10}285bitcoinPossible values: ethereumPossible values: the transaction fee paid, in base units
nullExample: 17500Pattern: ^[0-9]*(\.[0-9]+)?$nullnullMax fees represent the highest possible fee amount you will pay to broadcast this transaction, in base units. The final fees, calculated once the transaction is approved by the last Operator, might be lower, but will never exceed that amount. See https://help.vault.ledger.com/Content/transactions/tx.html for details
nullExample: 2100Pattern: ^[0-9]*(\.[0-9]+)?$null6nullExample: tb1q2tvjts80vthcywq9au2yynpezca57mvv0j7lzmOnly available once the transaction has been submitted to the blockchain
nullExample: ["0x0D9377F84af90e6936973aEF3063fe6e16ca693e"]nullExample: NORMALPossible values: PENDING_APPROVALPossible values: nullExample: cd199dd0c61ff75c7a442e425771fedfe07e191a76aed64b6a311ec4a369b20eSENDPossible values: nullInvalid transaction parameters
Transaction not found