/route
endpoint now supports cross-chain routing with the new destinationChainId
parameter. This enables seamless routing between any two positions across different chains:/account/{accountId}
endpoint returns the accountId used in on-chain events for your API key:/bundle
endpoint now returns route information similar to the /route
endpoint when bundled actions involve routing. This provides better transparency into the execution path of complex bundled transactions./route/nontokenized
endpoint now supports the referralCode
parameter, enabling referral tracking for non-tokenized position routing.route
API now supports destinationChainId
parameter that lets you do routing between any two positions on any two chains:projects
and protocols
/tokens
/projects
API links to protocols/projects
API recognizes overarching DeFi projects behind specific protocols.The API now returns:projectId
- the ID of the project, e.g. aave
,protocols
- the list of aave
protocols, e.g. aave-v3
, aave-static-atokens
, and aave-v2
chains
- the list of chain IDs the protocol is supported on by Enso./tokens
filters/tokens
endpoint is useful for filtering through 2,292,738 tokens recognized by Enso.
The new filters are:symbol
, e.g. BERA
or mooBeraswapBerachainUSDC.e/HONEY
name
, e.g. EVK Vault eUSDC.e-1
/prices
endpoint now has an option to fetch prices for multiple tokens in a single batch:EnsoRouter
and DelegateEnsoShortcuts
tx.to
from /route
and /bundle
endpoints to send the transaction to the correct contract address. This way, you won’t need to update your code with future upgrades.GET /route/nontokenized
endpoint enables automatic routing when entering non-tokenized positions.
For these transactions, a smart wallet is necessary, and routingStrategy: "delegate"
is necessary.
Explore:/tokens
API now implements cursor-based pagination for the GET /tokens
API endpoint, enabling more efficient retrieval of token data.