Skip to main content
POST
Returns pre-built transactions for the given route. It is assumed that transactions will be signed and sent by the sender via wallet

Authorizations

X-Api-Key
string
header
required

Body

application/json
sender_address
string
required
Example:

"UQCNTO0Nh0Z7QNyRW1BLWfk08f2dAOw4izrx9sO6OUPg4DoV"

paths
object[]
required

Value of this field is a response from route building endpoint

slippage
number<double>

If the slippage is exceeded, the transaction will not be executed and intermediate tokens will be returned to the sender.

Required range: 0 <= x <= 1
Example:

0.05

dynamic_slippage
boolean
default:false

If set to true, slippage will be calculated dynamically.

Example:

true

referral_name
string

May be set whilst building transactions from B2B partnership products

Example:

"tonkeeper"

custom_fee
object

If present, additional transaction for fees collection will be generated. Because of that, be careful with max_splits to not exceed wallet contract limits

mev_protection
boolean

Whether a MEV protection should be enabled

Example:

true

Response

transactions for the route

route_id
integer
required

Unique identifier of the route used for tracking.

transactions
object[]
required