# transaction

Transaction approvals, signed results and sending.

 - [POST /transactions/{transaction_id}/actions/send](https://docs.vilna.io/ru/apis/vks/api/transaction/send-transaction.md): Queue a signed transaction for submission to a blockchain node. The 202 response means the request was saved, not that the node accepted the transaction. Temporary failures and uncertain outcomes may
 - [GET /transactions/{transaction_id}/logs](https://docs.vilna.io/ru/apis/vks/api/transaction/list-transaction-logs.md): List send attempts for this transaction, newest first. Each entry describes one queued attempt to submit the signed transaction. A successful attempt means a node accepted it, not that it was confirme
 - [GET /transactions/{transaction_id}](https://docs.vilna.io/ru/apis/vks/api/transaction/get-transaction.md): Get transaction details, signer decisions and the signing status. The signed result and its hash become available when signing is complete.
 - [GET /transactions](https://docs.vilna.io/ru/apis/vks/api/transaction/list-transactions.md): List the account signing history with sorting and pagination, including signed results and any send time recorded by VKS.
 - [POST /transactions](https://docs.vilna.io/ru/apis/vks/api/transaction/create-transaction.md): Request approval and signing of a transaction. VKS assigns its transaction_id. Use an active account, a network supported by its address format, and one complete signing group from the vault. Supply t