Solana TPU Sender getting started

Get an API key

Message @supanode_tgs on Telegram and ask for a TPU Sender API key. Mention your preferred region and expected request rate. Supanode provides the key and connection details.

No monthly subscription. Request a free trial up to 24 hours from Supanode on Telegram; our team confirms availability and setup. Request a key and send transactions whenever needed. Tips are paid inside transactions.

Choose client access

• HTTP JSON-RPC: use the API key in a Bearer or X-Api-Key header. The steps below cover this integration.
• QUIK transport, port 8090: requires separate authorization. Send your public key to Supanode and request the transport-specific setup. Keep the private key local.

Both connect to TPU Sender for staked TPU delivery with SWQoS. See endpoints.

Prepare and submit over HTTP JSON-RPC

1. 1
   Build the transaction

   Fetch a recent blockhash from your normal RPC. Add your application instructions and a System Program transfer to an accepted tip account. The private minimum is 150,000 lamports (0.00015 SOL). Add a priority fee when your workload needs it.

2. 2
   Sign locally

   Sign with your application wallet, then serialize the transaction as base64. The API key authenticates the HTTP request; it is not part of the signed transaction.

3. 3
   Submit

   Call sendTransaction on your issued endpoint with Authorization: Bearer and your API key. See request examples.

4. 4
   Confirm separately

   Track the signature with getSignatureStatuses on your regular Solana RPC. Check both confirmationStatus and err.

Track the result

curl "$SOLANA_RPC_URL" \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"getSignatureStatuses","params":[["TRANSACTION_SIGNATURE"],{"searchTransactionHistory":true}]}'

A null status has no confirmation yet. A non-null err means execution failed. Choose the commitment level your application requires.

Keep the API key on your server. For access, key rotation and support, contact Supanode.