Submit transaction

curl --request POST \
  --url https://api.us1.shinami.com/aptos/node/v1/transactions \
  --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": [
      "<unknown>"
    ]
  },
  "signature": {
    "type": "ed25519_signature",
    "public_key": 6.195948399647823e+76,
    "signature": 6.195948399647823e+76
  },
  "replay_protection_nonce": "32425224034"
}
'

{
  "hash": "<string>",
  "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": [
      "<unknown>"
    ]
  },
  "signature": {
    "type": "ed25519_signature",
    "public_key": 6.195948399647823e+76,
    "signature": 6.195948399647823e+76
  },
  "replay_protection_nonce": "32425224034"
}

Transactions

Submit transaction

This endpoint accepts transaction submissions in two formats.

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 of 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

Submit transaction

curl --request POST \
  --url https://api.us1.shinami.com/aptos/node/v1/transactions \
  --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": [
      "<unknown>"
    ]
  },
  "signature": {
    "type": "ed25519_signature",
    "public_key": 6.195948399647823e+76,
    "signature": 6.195948399647823e+76
  },
  "replay_protection_nonce": "32425224034"
}
'

{
  "hash": "<string>",
  "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": [
      "<unknown>"
    ]
  },
  "signature": {
    "type": "ed25519_signature",
    "public_key": 6.195948399647823e+76,
    "signature": 6.195948399647823e+76
  },
  "replay_protection_nonce": "32425224034"
}

Authorizations

Authorization

string

header

required

Authorization: Bearer SHINAMI_ACCESS_KEY.

Body

A request to submit a transaction

This requires a transaction and a signature of it

sender

string<hex>

required

A hex encoded 32 byte Aptos account address.

This is represented in a string as a 64 character hex string, sometimes shortened by stripping leading 0s, and adding a 0x.

For example, address 0x0000000000000000000000000000000000000000000000000000000000000001 is represented as 0x1.

Example:

6.195948399647823e+76

sequence_number

string<uint64>

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

Example:

"32425224034"

max_gas_amount

string<uint64>

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

Example:

"32425224034"

gas_unit_price

string<uint64>

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

Example:

"32425224034"

expiration_timestamp_secs

string<uint64>

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

Example:

"32425224034"

payload

object

required

Payload which runs a single entry function

Option 1
Option 2
Option 3
Option 4

Show child attributes

signature

object

required

A single Ed25519 signature

Show child attributes

replay_protection_nonce

string<uint64>

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

Example:

"32425224034"

Response

A transaction waiting in mempool

hash

string

required

sender

string<hex>

required

A hex encoded 32 byte Aptos account address.

This is represented in a string as a 64 character hex string, sometimes shortened by stripping leading 0s, and adding a 0x.

For example, address 0x0000000000000000000000000000000000000000000000000000000000000001 is represented as 0x1.

Example:

6.195948399647823e+76

sequence_number

string<uint64>

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

Example:

"32425224034"

max_gas_amount

string<uint64>

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

Example:

"32425224034"

gas_unit_price

string<uint64>

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

Example:

"32425224034"

expiration_timestamp_secs

string<uint64>

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

Example:

"32425224034"

payload

object

required

Payload which runs a single entry function

Option 1
Option 2
Option 3
Option 4

Show child attributes

signature

object

A single Ed25519 signature

Show child attributes

replay_protection_nonce

string<uint64>

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

Example:

"32425224034"

Get transactions

Get transaction by hash

Aptos

Movement

SUI

Submit transaction

Authorizations

Body

Response