Skip to main content
POST

SDK methods

Learn more about sending transactions using our SDKs here.
Idempotency on errors: On 4xx or 5xx, Privy caches the response and replays it for the same key. Generate a new key to retry after a server error. Policy violations are an exception and allow same-key retries.
The wallet RPC endpoint is a synchronous endpoint, and a successful response indicates that the transaction has been broadcasted to the network. Transactions may get broadcasted but still fail to be confirmed by the network. The endpoint does not wait for confirmation or retry if the transaction fails to be confirmed. To handle these scenarios, see our guide on speeding up transactions.

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: eth_sendTransaction
string
required
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.
string
string
Available options: ethereum

Returns

enum<string>
required
Available options: eth_sendTransaction
object
required