Page 1 of 1

Bridge Info for LI.FI Integration

General info on how LI.FI uses bridge APIs

API Endpoint

Base URL for your public API (e.g. https://api.dex.com/v1). Should support quoting and swap execution.

API Key

Alternatively, we can also provide fixed IP addresses of our servers.

API Docs

Explorer

Please list any API limitations

URIs

Route Discovery

Our system periodically checks which assets, chains, routes are available. This information is used in our routing to decide which tools to query for pricing information. Response times for those endpoints are not that important as they are used in worker jobs.

- Get available routes between chains, including
- supported tokens
- min/max transfer size, available liquidity
- estimated duration
- fees

Suggested URI: /routes

- (optional) get bridge configs
- fee parameters / calculation
- confirmations per chain required / duration
- used contract addresses
- ABIs Suggested URI: /config

Does your API satisfy our route discovery requirements?

Does your API satisfy our route discovery requirements?
A
B

Quoting

- Get quote for a specific transfer Similar to our quote endpoint: https://apidocs.li.fi/reference/get_v1-quote We request with: - fromChain - toChain - fromToken - toToken - toAddress (receiver) - fromAmount - slippage (0.005 represents 0.5%)
And expect a response containing:
- toAmount (expected output)
- toAmountMin (minimal output possible because of slippage)
- executionDuration (how many seconds will the transfer take after the source transactions is mined)
- gasEstimate (how many gas units does the interaction with your contract require)
- feeCosts (array of costs)
- parameters needed to be passed to your contract (not the compiled callData)
- (optional) deadline (if the rate expires after some time)
Suggested URI: GET /quote

Does your API satisfy our quoting requirements?

Does your API satisfy our quoting requirements?
A
B

Transfer Status

After an executed a transfer on-chain we will index it and check your API for the bridging status. We periodically call this endpoint to check if the funds were received on the destination chain.
- Get status of submitted transfer Based on submitted transaction hash on the source chain Gathers information for our https://apidocs.li.fi/reference/get_v1-status endpoint
Expected response:
- status - substatus (see https://docs.li.fi/li.fi-api/li.fi-api/status-of-a-transaction#the-different-sub-statuses-and-what-they-mean) - receiving: - txHash - chainId - tokenAddress - tokenAmount
Suggested URI: GET /transaction/{txHash}

Does your API satisfy our transfer status requirements?

Does your API satisfy our transfer status requirements?
A
B

Other optional endpoints

- Optional: get overall bridge status (uptime, changes, planned maintenance, …)
Suggested URI:
/health
- Optional: get bridge stats (volume, transaction, transaction speed all based on different time frames and for each route between assets/chains)
Suggested URI:
/statistics
- Optional: get stats about collected referral fees (if applicable)
Suggested URI:
/referral

Please provide any relevant details

Which chains are you live on?

Which chains are you live on?

Which upcoming chains do you plan to deploy on?

Which upcoming chains do you plan to deploy on?

Please list any routes between chains that you are live on that are not currently supported

Please provide contract addresses for each chain you are deployed on

Please list all relevant smart contract function calls with descriptions

How do you calculate fees?

How long do transfers take?

Please explain why (eg/ waiting for confirmations)

How do you handle refunds in case of a stuck transaction?

Please provide a link to your stats

How can we reach out for technical support?