Developer quickstart

What you can do

• Request quotes and authorize trades on both venues, 1inch Aqua and Uniswap V4
• Execute swaps through AquaSwapVMRouter or via a Uniswap V4 pool
• Manage LP liquidity locks and withdrawals through prepared calldata endpoints
• Track swap and withdraw lifecycle through poll endpoints

Read endpoints require the X-API-Key header. Signing endpoints such as /api/swap/authorize require the operator credential issued alongside your integration, and reject the read key.

Both venues share one namespace, /api/swap/*, with a venue field in the request body selecting the fill path.

Single-chain 1inch Aqua trader

POST /api/swap/quote?chainId=8453     { "venue": "aqua", "classId": "1", ... }
POST /api/swap/prepare?chainId=8453   { "venue": "aqua", "classId": "1", ... }

For the aqua venue, chainId rides the query string. /quote sizes the trade. /prepare returns calldata for AquaSwapVMRouter.swap(order, tokenIn, tokenOut, amount, takerTraitsAndData). Submit the prepared transaction yourself.

The router emits Swapped(orderHash, maker, taker, tokenIn, tokenOut, amountIn, amountOut) on success. The backend indexes this event and credits LP attribution, so no further client action is required.

Uniswap V4 trader

POST /api/swap/quote      { "venue": "v4", "chainId": 8453, ... }
POST /api/swap/authorize  { "venue": "v4", "chainId": 8453, ... }

/quote prices a just-in-time (JIT) liquidity fill against Aqua0's own vault capital. /authorize returns an EIP-712-signed authorization bound to that exact swap. Submit a Uniswap V4 swap with the authorization as hookData. The pool's hook validates it and injects a temporary liquidity range, then settles and emits a settlement event when the swap completes.

The liquidity behind a fill may be locked on another chain. That backing is invisible to the trader and needs no client action after the swap lands, see Concepts for how it settles.

Liquidity provider lock and withdraw

POST /api/vaults/:chainId/:asset/prepare-deposit
POST /api/vaults/:chainId/:asset/prepare-withdraw

Both return calldata for you to sign yourself. prepare-deposit includes an approval call first when one is needed (requiresApproval on the response tells you). prepare-withdraw covers your idle principal (freePrincipal on the response) and withdraws instantly, while principal currently backing a strategy withdraws through the async request/claim path instead, see Async redeem semantics for the timing guarantee.

Full route surface

See the API Reference for the full request/response surface. This page documents the endpoints integrators reach for first.

Next steps

• Read Concepts for the vault, class, and attribution model.
• Read Integration for recommended UX patterns.
• Read Status and errors for lifecycle states and retry guidance.