logsSubscribe

logsSubscribe opens a Solana PubSub subscription that pushes the log lines emitted by transactions as they are processed on the network. Each notification carries the transaction signature, any error, and the array of program log messages — the same Program log: output a program writes while it runs on this SOL-fee-paid chain. You can take every transaction's logs or narrow to those that mention one account or program. The matching JSON-RPC endpoint is https://solana.therpc.io/YOUR_API_KEY, and you stop the stream by passing the returned subscription id to logsUnsubscribe.

Use cases

• Tail the logs of every transaction that mentions a specific program or account by passing { mentions: [pubkey] } — for instance a Raydium AMM or a token mint.
• Drive a live event feed by parsing the Program log: lines that programs emit, surfacing swaps, mints, or stake events as they happen.
• Detect a specific instruction firing by matching the log text, so you can trigger downstream work the instant it appears.

Parameters

Response

Example request

1# Open a WebSocket connection (e.g. with wscat) and send the subscribe request:
2wscat -c wss://solana.therpc.io/YOUR_API_KEY
3# then send:
4> {"jsonrpc":"2.0","id":1,"method":"logsSubscribe","params":[{},{}]}

Errors & troubleshooting

Common pitfalls

• The mentions filter takes exactly one pubkey inside the array — Solana rejects a list of several addresses, so open one subscription per address you want to follow.
• The "all" filter is extremely high volume on a chain producing slots every ~400ms — prefer a mentions filter to keep the stream manageable, and call logsUnsubscribe with the subscription id when you are finished.

Supported networks

• Mainnet
• Devnet

See also

• signatureSubscribe
• getTransaction