getSignatureStatuses

After you broadcast a Solana transaction you need to know whether it landed, and getSignatureStatuses answers that for up to 256 signatures in one call. For each signature it returns the slot it was processed in, a confirmations count, any execution err, and a confirmationStatus of processed, confirmed, or finalized — or null if the node has never seen that signature. It is the standard polling companion to sendTransaction for SOL and SPL token transfers. Call it on TheRPC at https://solana.therpc.io/YOUR_API_KEY.

Use cases

• Poll a signature returned by sendTransaction until its confirmationStatus reaches confirmed or finalized before you treat the transfer as done.
• Check a whole batch of in-flight signatures in one request inside a sending service, instead of one round trip per transaction.
• Tell a dropped transaction apart from a failed one: a null entry means the cluster never saw it (so resend), while an entry with err set means it executed and failed (so do not blindly resend).

Parameters

Response

Example request

1curl https://solana.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5  "jsonrpc": "2.0",
6  "id": 1,
7  "method": "getSignatureStatuses",
8  "params": [
9    [],
10    {}
11  ]
12}'

Errors & troubleshooting

Common pitfalls

• By default the node only checks recent signatures. For older ones, set searchTransactionHistory: true, which also searches long-term storage and is noticeably heavier.
• A null entry means the node has not seen that signature — it does not mean the transaction failed. Read err on a non-null entry to detect actual failure.
• The cap is 256 signatures per call; split a larger set into chunks of 256 or fewer.

Supported networks

• Mainnet
• Devnet

See also

• getSignaturesForAddress
• getTransaction
• sendTransaction