API Reference
Source Code
Caching & Liveness
API Endpoints
Type of trade. Use minOutput, exactInput or exactOutput.
exactInputPossible values: Required amount of output token in smallest unit.
1000000Address of the input token on the origin chain.
0x0b2C639c533813f4Aa9D7837CAf62653d097Ff85Address of the output token on the destination chain.
0x82aF49447D8a07e3bd95BD0d56f35241523fBab1Chain ID of the origin chain.
10Chain ID of the destination chain.
42161Address of the depositor initiating the swap.
0xA4d353BBc130cbeF1811f27ac70989F9d568CeABAddress of the account receiving the output token.
0xA4d353BBc130cbeF1811f27ac70989F9d568CeAB2-byte hex-string that identifies the integrator. E.g., "0xdead".
0xdeadAddress to receive refunds. Defaults to depositor if not provided.
0xDEPOSITOR_ADDRESSSpecifies whether refund should be sent on the origin chain. Defaults to true.
trueSlippage tolerance percentage (e.g., 1 for 1%, 0.5 for 0.5%).
1Swap approval data returned successfully.
Bad request due to invalid input parameter.
Learn how to integrate the /swap/approval Endpoint
/swap/approval EndpointPlanned Advancements
Returns transfer limits for inputToken+outputToken, originChainId, and destinationChainId.
Address of token to bridge on the origin chain. Must be used together with parameter outputToken. For ETH, use the wrapped address, like WETH.
Note that the address provided must exist on the specified originChainId.
0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2Address of token to bridge on the destination chain. Must be used together with parameter inputToken. For ETH, use the wrapped address, like WETH.
Note that the address provided must match the token address on the specified destinationChainId below.
0x4200000000000000000000000000000000000006Chain ID where the specified token or inputToken exists.
1The intended destination chain ID of the bridge transfer.
10Transfer limits
Invalid input
Unexpected error within the API
Returns the fill status of a deposit along with a corresponding fill transaction hash if filled.
This endpoint loads data queried by an indexing service that polls relevant events on a 10-second cadence. Users should therefore expect an average latency of 1 to 15 seconds after submitting a deposit to see the status changed in this endpoint. This delay comes from the time it takes for the internal indexing to include the deposit transaction.
Chain Id where the deposit originated from.
137The deposit id that is emitted from the DepositV3 function call as a V3FundsDeposited event.
1349975Lifecycle of a transaction
Lifecycle of a transaction
Maximum number of deposits to return in a single request; used for pagination.
50Number of deposits to skip from the beginning of the result set; used for pagination.
100Wallet address of the depositor; filters results to deposits made by this address.
0x89f423567c2648BB828c3997f60c47b54f57Fa6eList of deposits for a given depositor
List of deposits for a given depositor
Last updated