Submit batch transactions

curl --request POST \
  --url https://api.us1.shinami.com/aptos/node/v1/transactions/batch \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '[
  {
    "sender": 6.195948399647823e+76,
    "sequence_number": "32425224034",
    "max_gas_amount": "32425224034",
    "gas_unit_price": "32425224034",
    "expiration_timestamp_secs": "32425224034",
    "payload": {
      "type": "entry_function_payload",
      "function": "0x1::aptos_coin::transfer",
      "type_arguments": [
        "<string>"
      ],
      "arguments": [
        "<any>"
      ]
    },
    "replay_protection_nonce": "32425224034",
    "signature": {
      "type": "ed25519_signature",
      "public_key": 6.195948399647823e+76,
      "signature": 6.195948399647823e+76
    }
  }
]'

{
  "transaction_failures": [
    {
      "error": {
        "message": "<string>",
        "error_code": "account_not_found",
        "vm_error_code": 123
      },
      "transaction_index": 123
    }
  ]
}

Transactions

Submit batch transactions

This allows you to submit multiple transactions. The response has three outcomes:

All transactions succeed, and it will return a 202
Some transactions succeed, and it will return the failed transactions and a 206
No transactions succeed, and it will also return the failed transactions and a 206

To submit a transaction as JSON, you must submit a SubmitTransactionRequest. To build this request, do the following:

Encode the transaction as BCS. If you are using a language that has native BCS support, make sure to use that library. If not, you may take advantage of /transactions/encode_submission. When using this endpoint, make sure you trust the node you’re talking to, as it is possible they could manipulate your request.
Sign the encoded transaction and use it to create a TransactionSignature.
Submit the request. Make sure to use the “application/json” Content-Type.

To submit a transaction as BCS, you must submit a SignedTransaction encoded as BCS. See SignedTransaction in types/src/transaction/mod.rs. Make sure to use the application/x.aptos.signed_transaction+bcs Content-Type.

POST

transactions

batch

Submit batch transactions

curl --request POST \
  --url https://api.us1.shinami.com/aptos/node/v1/transactions/batch \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '[
  {
    "sender": 6.195948399647823e+76,
    "sequence_number": "32425224034",
    "max_gas_amount": "32425224034",
    "gas_unit_price": "32425224034",
    "expiration_timestamp_secs": "32425224034",
    "payload": {
      "type": "entry_function_payload",
      "function": "0x1::aptos_coin::transfer",
      "type_arguments": [
        "<string>"
      ],
      "arguments": [
        "<any>"
      ]
    },
    "replay_protection_nonce": "32425224034",
    "signature": {
      "type": "ed25519_signature",
      "public_key": 6.195948399647823e+76,
      "signature": 6.195948399647823e+76
    }
  }
]'

{
  "transaction_failures": [
    {
      "error": {
        "message": "<string>",
        "error_code": "account_not_found",
        "vm_error_code": 123
      },
      "transaction_index": 123
    }
  ]
}

Authorizations

Authorization

string

header

required

Body

sender

string<hex>

required

Example:

sequence_number

string<uint64>

required

Example:

max_gas_amount

string<uint64>

required

Example:

gas_unit_price

string<uint64>

required

Example:

expiration_timestamp_secs

string<uint64>

required

Example:

payload

object

required

Option 1
Option 2
Option 3
Option 4

Show child attributes

signature

object

required

Option 1
Option 2
Option 3
Option 4
Option 5
Option 6
Option 7
Option 8
Option 9
Option 10
Option 11

Show child attributes

replay_protection_nonce

string<uint64>

Example:

Response

transaction_failures

object[]

required

Show child attributes

Get account transaction summaries

Simulate transaction

Aptos

Movement

SUI

Submit batch transactions

Authorizations

Body

Response