Zap lets users go from any token into a DeFi position (lending, staking, LP, etc.) in a single transaction on Solana.
Key differences from EVM:
- No token approvals needed, Solana SPL tokens don’t require a separate approval step
- Transactions are base64-encoded Solana transactions, not EVM calldata
- Some transactions are routed through Jito for MEV protection
- Multiple transactions in one operation use Solana’s
signAllTransactions
Chain ID
Use 7565164 as both srcChainId and destChainId for Solana.
Step 1, Get Quote
Use getZapQuote to fetch the best route for your zap.
Key Response Fields
Step 2, Execute Zap
Use zap to build and execute the transaction. The SDK returns base64-encoded Solana transactions that you sign and send.
Key Response Fields
data may contain more than one transaction. Each must be signed and sent in order.
Step 3, Sign and Send
The signing and sending method depends on two things: how many transactions there are, and whether isJitoTx is true.
Single transaction (non-Jito)
Multiple transactions
If step.data contains more than one transaction, sign all of them at once using signAllTransactions.
When isJitoTx: true
Jito transactions need to go through a Jito block engine. The SDK’s zap method handles this automatically, it returns the transaction ready for Jito submission. Sign and send via your Jito provider.
Broadcast decision summary
Step 4, Track Status
Use getZapTxnStatus to check the zap status using the txnId from the zap result.
For operations that may take a few seconds to confirm, poll until you reach a terminal state.
Status values
API Reference
The SDK wraps these endpoints:
Full Example
Last modified on July 29, 2026