Solana
signAndSendTransaction
Sign and send transaction with a Solana wallet using the signAndSendTransaction method.
POST
Documentation Index
Fetch the complete documentation index at: https://docs.privy.io/llms.txt
Use this file to discover all available pages before exploring further.
SDK methods
Learn more about sending transactions using our SDKs here.Headers
ID of your Privy app.
Request authorization signature. If multiple signatures are required, they should be comma
separated.
Request expiry. Value is a Unix timestamp in milliseconds representing the deadline by which the
request must be processed.
Path Parameters
ID of the wallet to get.
Body
Available options:
signAndSendTransactionAvailable options:
solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp (Solana Mainnet),
solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1 (Solana Devnet),
solana:4uhcVJyU9pJkvQyS88uRDiswHXSCkY3z (Solana Testnet)Optional parameter to enable gas sponsorship for this transaction. Learn
more.
Optional developer-provided reference ID for transaction reconciliation. Must be unique per
transaction and up to 64 characters. Use this to correlate transactions with your own internal
records. The
reference_id is included in transaction
webhook payloads and can be used to look up
transactions.Optional. If set to true, the signed transaction will be immediately returned after the enclave
signs, and submission to the network will happen asynchronously. Useful if you want to minimize
E2E latency, or if you want to submit to multiple endpoints to get the best transaction landing
time possible. Note that enabling this option also disables network preflight checks to minimize
latency, which means an invalid transaction will not return an error in the API response and will
not fire webhooks. You are responsible for validating a transaction, which can be done against a
Solana RPC endpoint.
Returns
Available options:
signAndSendTransaction
