🌐Quick start

This guide outlines two approaches for interacting with the Akka Router API for performing token swaps

Recommended: Solution 1 – Quote API (No Wallet Address Required)

Why Use This?

• No need for user's wallet address

• No requirement for token approval or balance check

• Ideal for frontend previews, estimations, and UX design

• Enables faster and safer integration during early stages of interaction

Sample Endpoint

https://routerv2.akka.finance/v2/1116/pks-quote

Sample URL

https://routerv2.akka.finance/v2/1116/pks-quote?src=0x900101d06A7426441Ae63e9AB3B9b0F63Be145F1&dst=0x9410e8052Bc661041e5cB27fDf7d9e9e842af2aa&amount=100000&slippage=50

Required Parameters

src: Source token address

dst: Destination token address

amount: Amount of source token (in smallest unit)

slippage: Slippage tolerance (e.g. 50 = 0.5%)

Response

Includes a swapData object with contract call data for execution

Lightweight and secure: no state checks on user wallet

Alternative: Solution 2 – Swap API (Wallet Address Required)

When to Use

Use this only when you're ready to submit a transaction on-chain and have access to:

• User’s wallet address

• Approved token allowance

• Sufficient balance

Sample Endpoint

https://routerv2.akka.finance/v2/1116/pks-quote

Sample URL

https://routerv2.akka.finance/v2/1116/pks-quote?src=0x900101d06A7426441Ae63e9AB3B9b0F63Be145F1&dst=0x9410e8052Bc661041e5cB27fDf7d9e9e842af2aa&amount=100000&slippage=50

Required Parameters

src: Source token address

dst: Destination token address

amount: Amount of source token

from: User wallet address

slippage: Slippage tolerance (in %)

includeTokensInfo: (optional) Boolean for including token metadata

includeProtocols: (optional) Boolean for including routing protocol details

Response

Includes a swapData field which outlines contract input parameters.

No user-specific validation or balance checks are performed.Step 3: Build the Body of the Transaction