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.
Required input amount in the smallest unit of the input token.
1065159719994Expected amount of output token.
940201830Minimum guaranteed amount of output token.
940201830Expected time in seconds to complete the swap.
8Bad 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
The minimum deposit size in the tokens' units. Note: USDC has 6 decimals, so this value would be the number of USDC multiplied by 1e6. For WETH, that would be 1e18.
7799819The maximum deposit size in the tokens' units. Note: The formatting of this number is the same as minDeposit.
22287428516241The max deposit size that can be relayed "instantly" on the destination chain. Instantly means that there is relayer capital readily available and that a relayer is expected to relay within seconds to 5 minutes of the deposit.
201958902363The max deposit size that can be relayed with a "short delay" on the destination chain. This means that there is relayer capital available on mainnet and that a relayer will immediately begin moving that capital over the canonical bridge to relay the deposit. Depending on the chain, the time for this can vary. Polygon is the worst case where it can take between 20 and 35 minutes for the relayer to receive the funds and relay. Arbitrum is much faster, with a range between 5 and 15 minutes. Note: if the transfer size is greater than this, the estimate should be between 2-4 hours for a slow relay to be processed from the mainnet pool.
2045367713809The recommended deposit size that can be relayed "instantly" on the destination chain. Instantly means that there is relayer capital readily available and that a relayer is expected to relay within seconds to 5 minutes of the deposit. Value is in the smallest unit of the respective token.
2045367713809Invalid 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
The status of the deposit.
- filled: Deposits with this status have been filled on the destination chain and the recipient should have received funds. A FilledV3Relay event was emitted on the destination chain SpokePool.
- pending: Deposit has not been filled yet.
- expired: Deposit has expired and will not be filled. Expired deposits will be refunded to the
depositoron theoriginChainIdin the next batch of repayments. - refunded: Deposit has expired and the depositor has been successfully refunded on the originChain.
- slowFillRequested: Deposit has been made but no relayer has filled the intent, therefore Across' relayer fills the userβs intent without requiring another relayer to front the capital. It's important that the input token and output token are the same asset here.
The transaction hash of the fill transaction on the destination chain. This field is only present when fillStatus is filled.
The chain id where the fill transaction will take place.
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
Internal unique identifier for the deposit record.
Hash of the relay data used to verify and track fill events.
Unique identifier assigned to the deposit event on the origin chain.
The chain ID where the deposit was originally made.
The target chain ID where the fill is expected to complete.
Wallet address of the user who initiated the deposit.
Wallet address intended to receive funds on the destination chain.
Address of the token deposited on the origin chain.
Amount of inputToken sent in the deposit (in wei).
Address of the token expected to be received on the destination chain.
Amount of outputToken expected to be received (in wei).
Optional arbitrary bytes message encoded with the deposit intent.
Hash of the message payload.
Address of the relayer granted exclusivity to fill the deposit, if any.
Timestamp indicating when relayer exclusivity expires.
Deadline by which the deposit must be filled before expiring.
Time at which the quote for the deposit was generated.
Transaction hash of the deposit on the origin chain.
Block number where the deposit transaction was confirmed.
Timestamp of the block containing the deposit transaction.
The status of the deposit fill lifecycle.
Transaction hash for refund if deposit expired and funds were returned to the depositor.
USD price of the token used in any optional swap.
Fee paid in USD for the optional swap (if performed).
Fee paid in USD for bridging the funds across chains.
USD price of the input token at the time of deposit.
USD price of the output token at the time of quote.
Gas cost incurred in native token units during fill.
USD value of the gas fee for filling the deposit.
USD price of the gas token on the destination chain at the time of fill.
Transaction hash for any token swap conducted on the destination chain.
Token address used in a swap on the destination chain, if any.
Amount of the swapToken exchanged, if a swap occurred.
Address of the relayer that submitted the fill on the destination chain.
Timestamp when the fill was confirmed on the destination chain.
Transaction hash of the actual fill transaction.
List of transaction hashes representing optional speedup fills.
List of deposits for a given depositor
Last updated