Skip to main content
POST
getSignaturesForAddress
curl --request POST \
  --url 'https://rpc-mainnet.solanatracker.io/?api_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "jsonrpc": "2.0",
  "id": "db16f277-1a22-41ff-9f85-f37e2cd77900",
  "method": "getSignaturesForAddress",
  "params": [
    "Vote111111111111111111111111111111111111111"
  ]
}
'
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": [
    {
      "signature": "5XXN7L7cMGYTvckcaNeTXxhJgxeT1JTa9auwa2yXCFR1NXzwXrXNAWx4SaAw48S5186VzvXiXVEsWJu1WFR5AAmg",
      "slot": 114,
      "err": null,
      "memo": null,
      "blockTime": null,
      "confirmationStatus": "finalized"
    }
  ]
}

Authorizations

ā€‹
api_key
string
query
required

Body

application/json
ā€‹
jsonrpc
enum<string>
default:2.0
required

The JSON-RPC protocol version.

Available options:
2.0
Example:

"2.0"

ā€‹
id
string
default:1
required

A unique identifier for the request.

Example:

"1"

ā€‹
method
enum<string>
default:getSignaturesForAddress
required

The name of the RPC method to invoke.

Available options:
getSignaturesForAddress
Example:

"getSignaturesForAddress"

ā€‹
params
(string | object)[]
required

Array containing the required account address and optional configuration object.

Solana account address to retrieve transaction history for (wallet, token, program, NFT, etc.).

Example:

"Vote111111111111111111111111111111111111111"

Response

200 - application/json

Successfully retrieved signatures for the specified address.

ā€‹
jsonrpc
enum<string>

The JSON-RPC protocol version.

Available options:
2.0
Example:

"2.0"

ā€‹
id
string

Identifier matching the request.

Example:

"1"

ā€‹
result
object[]

List of transaction signature information.