Skip to main content
GET
/
transactions
Get transactions
curl --request GET \
  --url https://api.us1.shinami.com/aptos/node/v1/transactions \
  --header 'Authorization: Bearer <token>'
[
  {
    "type": "pending_transaction",
    "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.

Query Parameters

​
start
string<uint64>

Ledger version to start list of transactions

If not provided, defaults to showing the latest transactions 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"

​
limit
integer<uint16>

Max number of transactions to retrieve.

If not provided, defaults to default page size

Response

A transaction waiting in mempool

​
type
enum<string>
required
Available options:
pending_transaction
Example:

"pending_transaction"

​
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

​
signature
object

A single Ed25519 signature

​
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"