Last updated
Last updated
Squid is launching v2! With this upgrade Squid delivers:
Lightning fast response times, always <1 sec, down to 300ms
Long term scaling improvements, we’re ready to handle hundreds of RPS
Each partner has an RPS limit in place, so please let us know if you need more!
As a part of this upgrade there are breaking changes you must implement to get access to the improved Squid v2
Change your endpoint from to
Route Request Endpoint:
Transaction Status Endpoint:
Acquiring a v2 Integrator ID. Connect with the Squid team and we will enable your existing integratorID from a v1 Integrator ID to a v2Integrator ID.
If you do not have a V1 Integrator ID to upgrade, you can and it will be sent to your email.
Modify your hook implementations
Including a fundAmount
and fundToken
to preHooks
Include provider
, description
, and logoURI
in both the preHook and postHook call
V1: Ethers V5
V2: Ethers V5 or V6 up to v6.7.1
npm i ethers@6.7.1
The /route endpoint is now POST. /status is still a /GET request.
Our SDK handles this behind the scenes. No changes needed
v1:
v2: Slightly different import path
integrator-id
is required on all requests in v2v1
v2
The route request now uses the new endpoint and requires the updated Integrator ID in the headers.
Note the extraction of requestId from the response headers, which is now required for status checks.
The status check endpoint has also been updated:
Ensure you're passing the requestId obtained from the route request.
Include slippage
as a number instead of an object
Extract requestId
from response headers for status checks
Use route.transactionRequest
for transaction execution
Initialize the SDK with the new base URL and your updated Integrator ID:
The getRoute method now returns a requestId along with the route:
Use the transactionRequest object from the route to execute the transaction:
Include the requestId when checking the transaction status:
customContractCalls
have been renamed to postHook
and postHook
Hooks now require additional parameters. Here are examples for both pre and postHooks:
You can use a preHook to execute an action before a cross-chain swap.
You can use a preHook to execute an action after a cross-chain swap.
There are two required modifications to Request Params
slippage: NUMBER(0.01-99.99);
this number can be 0.01 to 99.99 and represents the associated slippage with a transaction. This parameter is now optional and will be dynamically set by Squid if not included.
Request Params Modification Example for SDK
we have added a fundAmount
and fundToken
to preHooks. We have also added a provider
, description
, and logoURI
to the both the preHook and postHook call.
Modified Hook Implementation SDK
Lastly, the request response shape has changed inside the actions steps. This is for integrators that utilize the request response.
Wrappers, bridges, and DEXes will now have an associated Provider:
and logoURI:
within the json response.
Migrating from v1 to v2, enables route requests under 1 second and sustainability scalability.. You can find out-of-the-box examples to implement Squid v2 in our
If you're using the Squid SDK, you can find the key changes to implement below. You can find out-of-the-box examples to implement Squid v2 and our SDK in our