Skip to main content
You send a transaction with one call, ethSendTransaction or solSendTransaction, and get back a sendTransactionStatusId. Turnkey constructs, signs, and broadcasts the transaction; you then poll the status ID, or receive a webhook, until it lands. See Overview for what Turnkey handles for you.

Prerequisites

  • A Pay-as-you-go, Pro, or Enterprise plan.
  • A wallet account on a supported chain.
  • To sponsor the transaction, Gas Sponsorship enabled for your organization. See Gas sponsorship and spend limits.
  • Otherwise, enough of the chain’s native token in the wallet to pay for gas.

Choose an SDK

Other SDKs, such as Go, Python, Rust, Swift, and Kotlin, send the same eth_send_transaction and sol_send_transaction activities. See the SDK reference.

Send an EVM transaction

Configure the provider once:
Then send from a component:
handleSendTransaction opens Turnkey’s modal, polls until the transaction is INCLUDED, and shows a success screen with an explorer link. To build your own UI, call ethSendTransaction and pollTransactionStatus from useTurnkey() instead. They take the same parameters as in the @turnkey/core tab.
A transaction can carry calldata, so you can call contracts, deploy them, or run any valid EVM operation. Omitted fields, such as nonce and fees, are filled in for you. For sponsored transactions, Turnkey always sets the nonce and fees, so do not pass them.

Batch EVM calls

Pass up to 50 entries in calls, instead of to, value, and data, to send them as one atomic transaction. The calls run in order from your wallet’s address, and if any of them reverts, none take effect. A batch is one activity, so it is one policy decision and, if your policies require it, one approval. Each call is still evaluated against your policies on its own, and the batch is allowed only if every call is allowed.
handleSendTransaction accepts the same calls array. With @turnkey/sdk-server, pass calls at the top level, as in the server example above. Every batch, sponsored or not, runs through an EIP-7702 delegation to Turnkey’s gas station delegate, because a plain wallet cannot run several calls in one transaction. Turnkey signs the delegation for you the first time a wallet batches on a chain. With sponsor: false, the wallet pays the gas, as it does for a single transaction. Tempo is the exception: it supports batches natively, so Tempo batches use no delegation and no gasStationNonce.
  • Sponsored batches: calldata across all calls is capped at 64 KiB, and Turnkey sets the nonce and fees.
  • Non-sponsored batches: gasLimit is required, because later calls can depend on earlier ones and cannot be estimated one by one.
  • Replay protection: batches use a nonce on the gas station delegate, which Turnkey fetches if you omit gasStationNonce. To include it in the signed request, fetch it with get_nonces and pass it as gasStationNonce.
See atomic-batch-with-aave and with-scoped-deposit-session for complete examples, and Broadcast EVM transaction for every field.

Send a Solana transaction

You build the unsigned transaction, and Turnkey signs it with the listed signers, adds a recent blockhash if you omit one, and broadcasts it.
signWiths lists every required signer in transaction order. For transaction versions, signature slots, size limits, and compute and fee controls, see Solana transactions.
Turnkey signs the transaction you build, so your application is still responsible for validating its contents. Before sponsoring a transaction that may create accounts, enable Sponsor Solana Rent in the dashboard, and check whether the transaction creates or closes accounts or routes rent refunds back to the signer. See Solana Rent Sponsorship and Solana transaction construction for sponsored flows.

Chain-specific notes

Monad

Sponsored transactions and batches delegate your wallet with EIP-7702. On Monad (eip155:143 and eip155:10143), delegated wallets have extra rules:
  • 10 MON balance reserve. A transaction that would reduce a delegated account’s balance below 10 MON unconditionally reverts. This is not a minimum balance requirement — an account can hold less than 10 MON and still transact, as long as the transaction leaves its balance unchanged or higher. For example, a delegated EOA holding 5 MON can be called by a gas sponsor and succeed as long as it ends with at least 5 MON.
  • No CREATE / CREATE2. These opcodes are not permitted while code executes in the context of a delegated EOA, and the call frame reverts if used. (A normal contract-creation transaction sent directly from the EOA, with no to field, is still allowed.)
See Monad’s EIP-7702 documentation for full details.

Next steps