Custom-Built Link
Builds an all-inclusive link that automatically has the amount, slippage, route, and so on all set and helps your users save time and effort.
Last updated
Builds an all-inclusive link that automatically has the amount, slippage, route, and so on all set and helps your users save time and effort.
Last updated
The XY Finance front-end technologies support URL query parameters to allow for the possibility of custom-designed links on XY Finance. Users will be able to take full advantage of this link to simplify the process of bridging tokens and save lots of time spent on prior arrangements for a bridging activity. This design is thoughtful in this seemingly complicated crypto trading world in that all you need to do is redefine the set of parameters attached to the end of a URL, which are extensions used to help define specific content or actions based on the data being passed.
Appending query parameters to the end of the link that defaults to the standard style (trading pairs, the amount, etc.) each time you open it is, though not the first-of-its-kind in this sector, the necessity that helps your project/platform pre-determine the bridge and the swapping route for users and allows you to get the most our of token swaps with XY Finance
Take a swap from USDC on Ethereum to USDC on Polygon.
Click the link below and view carefully the URL on the top of the webpage.
The token on the source/target chain, slippage tolerance rate, the routes picked out for the best user experience, everything is all set within this custom-made link. Most importantly, it saves your users from human errors which could stem from operating the system manually by themselves.
sourceChainId
Chain ID
1
targetChainId
Chain ID
137
fromTokenAddress
Token Contract Address
0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48
toTokenAddress
Token Contract Address
0x2791bca1f2de4661ed88a30c99a7a9449aa84174
amount
Float Value
50.5
The bespoke link only works if at least a valid chain id exists.
If the address provided is empty or invalid, the default token will be the native token.
The "sourceChainId" and "targetChainId" in the configuration can be found in the page below.
