TriportRPC
DashboardDocs

getSignaturesForAddress

Last updated:

getSignaturesForAddress returns a list of transaction signatures that reference the given account, ordered from newest to oldest (reverse chronological). It is the primary building block for reconstructing an account's transaction history: page through the signatures here, then fetch the full transactions with getTransaction for each one you care about.

Each entry is a lightweight SignatureInfo record — the signature itself plus the slot, success/failure status, optional memo, block time, and confirmation status. It does not include the transaction payload, so this call stays cheap even on busy accounts.

Results are paginated by signature, not by offset. A single call returns at most limit entries (default and maximum 1000). To walk further back in history, pass the oldest signature you received as before on the next call; to bound a scan to transactions newer than a known point, pass that signature as until.

Parameters

getSignaturesForAddress parameters
NameTypeRequiredDescription
addressPubkeyYes
configGetSignaturesForAddressConfigNo

Returns

getSignaturesForAddress return value
FieldType
resultarray

Examples

curl https://triport.io/sol \
  -X POST -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer <api-key>' \
  -d '{"id":1,"method":"getSignaturesForAddress","params":["EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",{"limit":1}],"jsonrpc":"2.0"}'
const res = await fetch("https://triport.io/sol", {
  method: "POST",
  headers: { "Content-Type": "application/json", Authorization: "Bearer <api-key>" },
  body: JSON.stringify({
  "id": 1,
  "method": "getSignaturesForAddress",
  "params": [
    "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
    {
      "limit": 1
    }
  ],
  "jsonrpc": "2.0"
}),
});
const data = await res.json();
import requests
resp = requests.post(
    "https://triport.io/sol",
    headers={"Authorization": "Bearer <api-key>"},
    json={"id":1,"method":"getSignaturesForAddress","params":["EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",{"limit":1}],"jsonrpc":"2.0"},
)
print(resp.json())
{
  "id": 1,
  "result": [
    {
      "err": {
        "InstructionError": [
          4,
          {
            "Custom": 6001
          }
        ]
      },
      "memo": null,
      "slot": 427699340,
      "blockTime": 1781948867,
      "signature": "4HMUm63GSfCuYoeA3kNmW41XK1AvzEuAserwBiGtr31GnVMCcZ9YSAbN9h7J148fVQWDLJZVGTjrzT56kvoKX5UH",
      "transactionIndex": 1455,
      "confirmationStatus": "finalized"
    }
  ],
  "jsonrpc": "2.0"
}

Usage

  1. Transport: HTTP (JSON-RPC).
  2. Networks: mainnet, devnet, testnet.
  3. Credit cost: 1 per call.

FAQ

What does getSignaturesForAddress do?
Returns the signatures of confirmed transactions that include the given address, newest first.
How many credits does getSignaturesForAddress cost?
getSignaturesForAddress costs 1 credit(s) per call on Triport by default.
Is getSignaturesForAddress available over WebSocket?
getSignaturesForAddress is an HTTP JSON-RPC method.