Solana
signAndSendTransaction
Sign and send transaction with a Solana wallet using the signAndSendTransaction method.
POST
SDK methods
Learn more about sending transactions using our SDKs here.Headers
string
required
ID of your Privy app.
string
Request authorization signature. If multiple signatures are required, they should be comma
separated.
string
Request expiry. Value is a Unix timestamp in milliseconds representing the deadline by which the
request must be processed.
Path Parameters
string
required
ID of the wallet to get.
Body
string
required
Available options:
signAndSendTransactionstring
required
Available options:
solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp (Solana Mainnet),
solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1 (Solana Devnet),
solana:4uhcVJyU9pJkvQyS88uRDiswHXSCkY3z (Solana Testnet)object
required
boolean
Optional parameter to enable gas sponsorship for this transaction. Learn
more.
string
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.boolean
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 rebroadcasting and validating the transaction, which
can be done against a Solana RPC endpoint using the
signed_transaction from the response.Returns
enum<string>
required
Available options:
signAndSendTransactionobject
required

