Body
The response from the quote endpoint
Base58-encoded address of the swapper's wallet
Compute unit price in micro-lamports. Mutually exclusive with prioritizationFeeLamports
.
x >= 0
If the fee account isn't a referral token account derived from the seeds
["referral_ata", referral_account, mint]
and the Referral program ID
REFER4ZgmyYx9c6He5XfaTMiGfdLwRnkV4RPp9t9iF3
, this should be unspecified. If specified, the
transaction will create the fee_account
if it doesn't already exist. The user pays for the
creation of the fee account. Ignored if fee_account
is unspecified.
The account that will receive the output token. If not specified, the user's associated token account for the output mint will be used. Allowed values are:
- A base58-encoded address, which specifies the address of the destination token account or, if the output is native SOL, the destination wallet. If the output isn't native SOL, the specified account must exist before the swap executes, or else the swap will fail.
- An object which specifies the owner of the destination token account. In this case, the
owner's associated token account for the output mint will be used as the destination token
account. Note that this cannot be used if the output is native SOL. The object contains
the following:
associatedTokenAccount
- objectowner
- base58-encoded address of the owner of the destination token account Use the specified owner's associated token account for the output mint as the destination token account. If the destination token account is uninitialized at swap execution time, the swap will create it. This cannot be used if the output is native SOL.
- Option 1
- Option 2
If true, the server will simulate the transaction to determine its compute unit limit. If unspecified or false, the transaction will use the default compute unit limit.
Base58-encoded address of the token account that will receive the platform fee if a platform fee applies to the swap. If specified, this account's mint must match the fee mint for the swap.
If true, the transaction will include a Jito sandwich mitigation account. The account will
be included in the SetComputeUnitLimit
instruction.
See https://docs.jito.wtf/lowlatencytxnsend/#sandwich-mitigation for more details.
Positive slippage fee parameters. If specified, then the swap will pay some or all positive slippage to the specified account.
If true, the transaction will never attempt to close the input token account
Prioritization fee in lamports. Mutually exclusive with computeUnitPriceMicroLamports
.
If both computeUnitPriceMicroLamports
and prioritizationFeeLamports
are unspecified, the
default of prioritizationFeeLamports="auto"
will be used.
Allowed values are:
- a u32 which specifies the lamports
- the string value "auto", where the server determines the fee automatically, capped at 0.005 SOL
- the string value "disabled", where the server leaves the prioritization fee unspecified
- an object containing the following
priorityLevelWithMaxLamports
- objectpriorityLevel
- string, eithermedium
,high
, orveryHigh
maxLamports
- integer, a cap on the prioritization fee
- an object containing the following
autoMultiplier
- a u32 which specifies how much to multiply the automatically determined fee by. The total prioritization fee will be capped at 0.005 SOL. A multiplier applied to the automatically-determined fee. The total is capped at 0.005 SOL.
Base58-encoded address of the sponsor's wallet. If specified, the sponsor will pay the transaction fee and for token account creation, and both the user and the sponsor must sign the swap transaction. This can be used to implement gasless swaps.
If false, the transaction will use wrapped SOL
Response
Imperative swap transaction
Compute unit limit assigned to the transaction
x >= 0
The last block height at which the transaction is valid
x >= 0
Prioritization fee in lamports
x >= 0
Base64-encoded swap transaction. The user must sign before sending it to Solana.
Prioritization fee type for the transaction Prioritization fee specified via the compute budget program