Skip to main content

/v1/submit_transactions REST API Endpoint

The submit transaction method allows users to send transactions to the FullNode DevNet platform by providing necessary transaction details in the request body and receiving a response containing the transaction information.

Updated on
Oct 4, 2023

/v1/submit_transactions REST API Endpoint

You can read here on how to generate and submit transactions to the Aptos blockchain, and verify these submitted transactions.

Body Parameters

sender
string
REQUIRED
The account from which the transaction was sent
sequence_number
string
REQUIRED
The sequence of a transaction sent by the specific sender
max_gas_amount
string
REQUIRED
The maximum amount of gas allocated for the execution of a transaction
gas_unit_price
string
REQUIRED
The cost per unit of gas, determining the transaction fee paid by the sender for each unit of computational resource consumed
expiration_timestamp_secs
string
REQUIRED
The timestamp indicating the expiration period of a transaction, specifying the time until which the transaction can be included in a block
payload
object
REQUIRED
The data that is being carried by a transaction. It contains the following fields:
type
string
The type of payload indicating the purpose of the data contained
function
string
The function associated with the payload
type_arguments
array
An array specifying the types of arguments provided to the function
arguments
array
An array containing the actual arguments passed to the function
signature
object
REQUIRED
An array with the following fields:
type
string
The type of signature used to verify the authenticity of the function
public_key
string
The public key associated with the account that generated the signature, used for verifying the signature's validity
signature
string
The actual signature generated using the private key corresponding to the public key provided

Returns

hash
The hash of the transaction
sender
The account from which the transaction was sent
sequence_number
The sequence of a transaction sent by the specific sender
max_gas_amount
The maximum amount of gas allocated for the execution of a transaction
gas_unit_price
The cost per unit of gas, determining the transaction fee paid by the sender for each unit of computational resource consumed
expiration_timestamp_secs
The timestamp indicating the expiration period of a transaction, specifying the time until which the transaction can be included in a block
payload
The data that is being carried by a transaction. It contains the following fields:
type
The type of payload indicating the purpose of the data contained
function
The function associated with the payload
type_arguments
An array specifying the types of arguments provided to the function
arguments
An array containing the actual arguments passed to the function
signature
An array with the following fields:
type
The type of signature used to verify the authenticity of the function
public_key
The public key associated with the account that generated the signature, used for verifying the signature's validity
signature
The actual signature generated using the private key corresponding to the public key provided
Request
1
curl --request POST \
2
  --url https://docs-demo.aptos-mainnet.quiknode.pro/v1/transactions \
3
  --header 'Accept: application/json, application/x-bcs' \
4
  --header 'Content-Type: application/json' \
5
  --data '{
6
  "sender": "SENDER_ADDRESS ",
7
  "sequence_number": "SEQUENCE_NUMBER",
8
  "max_gas_amount": "MAX_GAS_AMOUNT",
9
  "gas_unit_price": "GAS_UNIT_PRICE",
10
  "expiration_timestamp_secs": "EXPIRATION_TIMESTAMP_SECS",
11
  "payload": {
12
    "type": "PAYLOAD_TYPE",
13
    "function": "FUNCTION_NAME",
14
    "type_arguments": [
15
      "string"
16
    ],
17
    "arguments": [
18
      null
19
    ]
20
  },
21
  "signature": {
22
    "type": "SIGNATURE_TYPE",
23
    "public_key": "PUBLIC_KEY ",
24
    "signature": "SIGNATURE "
25
  }
26
}'
Don't have an account yet?
Create your QuickNode endpoint in seconds and start building
Get started for free