Common Instructions

Common instructions to compose with your swap transaction

When using /build, you can add your own instructions alongside the swap. This page covers common instructions and how to compose them.

Instruction ordering

When building your transaction, follow this order:

1. Compute budget instructions (from /build response)
2. Setup instructions (from /build response)
3. Your pre-swap instructions (e.g. create token accounts)
4. Swap instruction (from /build response)
5. Your post-swap instructions (e.g. transfer, memo, close accounts)
6. Cleanup instruction (from /build response, if present)

Create associated token account

If the recipient does not have a token account for the output mint, create one before the swap. Use createAssociatedTokenAccountIdempotent to safely handle the case where the account already exists.

import { getCreateAssociatedTokenIdempotentInstruction } from "@solana-program/associated-token";
import { TOKEN_PROGRAM_ADDRESS } from "@solana-program/token";

const createAtaIx = getCreateAssociatedTokenIdempotentInstruction({
  payer: signer,
  owner: address(recipientAddress),
  mint: address(outputMint),
  tokenProgram: TOKEN_PROGRAM_ADDRESS,
});

// Add before the swap instruction

Close token account

After a swap, you may want to close a token account to reclaim its rent. This is common when swapping to native SOL (the wrapped SOL account can be closed after unwrapping).

import { getCloseAccountInstruction } from "@solana-program/token";

const closeIx = getCloseAccountInstruction({
  account: address(tokenAccountToClose),
  destination: signer.address, // Rent refund destination
  owner: signer,
});

// Add after the swap instruction

SOL transfer

Add a SOL transfer to tip a validator, pay a fee, or send funds alongside the swap.

import { getTransferSolInstruction } from "@solana-program/system";

const transferIx = getTransferSolInstruction({
  source: signer,
  destination: address(recipientAddress),
  amount: 1_000_000n, // 0.001 SOL in lamports
});

// Add before or after the swap instruction

Memo instruction

Attach a memo to the transaction for tracking, tagging, or compliance purposes.

import { getAddMemoInstruction } from "@solana-program/memo";

const memoIx = getAddMemoInstruction({
  memo: "swap-order-12345",
});

// Add anywhere in the transaction

CPI (Cross-Program Invocation)

For protocols that need to invoke the Jupiter swap from within their own onchain program, use the swap instruction from /build as the inner instruction in a CPI call.

• How CPI works
• CPI considerations
  • CPI cannot use Address Lookup Tables (ALTs), which limits the number of accounts in the transaction. Jupiter’s complex routing often requires many accounts.
  • Use maxAccounts on /build to control route complexity and keep the transaction within size limits.
  • Set your own compute budget, as CPI adds overhead.
• Flash Fill (alternative to CPI): allows the use of Versioned Transactions and ALTs, avoiding the account limit constraints of CPI. The flow:
• References
  • CPI swap example
  • SOL swap CPI
  • Flash Fill example

Related

• Build for the full /build workflow
• Transaction Submission to submit via Jupiter’s transaction landing infrastructure with SOL tips for priority processing
• Advanced Techniques for compute unit simulation and priority fee strategies