YOUR APP. OUR ROUTE SEARCH.
Build with
better paths.
Quotes and unsigned swap transactions for Robinhood.
Compare routes. Protect the minimum. Keep control of signing.
POST /api/v1/quotePOST /api/v1/prepareOne API. Your execution.
BUILT FOR INTEGRATIONS
Everything around a swap.
Start with token discovery. Compare live routes, then prepare a wallet step with a protected minimum.
Download JavaScript client00 / ACCESS
Your keys. Your usage.
Sign in with your wallet to manage your API keys and usage. Your keys belong to your signed-in address. Access details are loading.
Open private feedback inboxYour integrations start here.
Connect an extension, open your wallet app, or scan a QR.
Create a key, run a quote and inspect the unsigned result.
Up to 5 active keys per account. Each key expires after 7 days.
Your key is ready.
This secret is shown once. Save it privately or use it in this tab.
Loading your keys…
What counts toward usage?
Quote and preparation requests share a limit of 6 per minute and 200 per UTC day for each key. Cached results, busy responses and failed searches count after a request is admitted. Retries beyond the limit are also counted as attempts. Requests rejected before admission do not count.
RPC budget is reserved in batches of up to 16 reads. Rejected reservation attempts are included. These units can exceed the work actually performed; this is not an Ankr credit count or a bill. Your keys share 200 request attempts and 10,000 RPC reserved units per UTC day. Limits are shared across your keys, so creating another does not reset your account budget. Server-wide limits may also apply. Unused reservations are not refunded. Usage refreshes after a playground request or when you select Refresh usage.
You see only keys created by your signed-in wallet. Signing out closes this session and clears keys from this tab; integrations keep working until you revoke their key or it expires. Older unassigned CLI keys stay separate.
PRIVATE / SITE FEEDBACK
Ideas from the community.
Only the site owner can read these messages. Contact details are shown exactly as submitted.
01 / PLAYGROUND
Make your first request.
Response
Waiting for a requestFind a path for your app.
Returned routes appear here, ranked by token output.
Network and approval gas are excluded.
Inspect JSON response
02 / PREPARE
From a route to a wallet step.
Wallet step
Nothing preparedReview before signing.
If an approval is needed, you receive that step first.
Each preparation includes a simulation of the returned step.
Inspect preparation JSON
03 / INTEGRATE
A quote in a few lines.
Send your key in the Authorization header. Use integer strings for amounts to preserve precision.
Direct routes are read at the returned block. KyberSwap uses its own snapshot. A response may contain only some sources; check their statuses.
After quoting, send quoteId, routeId, a public account and slippageBps to /api/v1/prepare. Quote selection lasts up to 2 minutes; preparation refreshes the price and preserves the original minimum floor. The response contains one unsigned wallet step.
Examples follow the pair and amount in the playground. Keep your API key on your server.
Keys under your control.
Sign in to key management to create and revoke your keys. Each integration has its own usage view. Secrets are saved outside the public build. Revocation applies to the next request, including cached quotes.
Start with the beta.
Access details are loading. Requests are free within the displayed limits; no credits or token payments are charged. The API never signs or broadcasts. Your integration must review each step, verify the wallet network and address, and refresh expired preparations.
Errors, expiry and the next wallet step
401 · UNAUTHORIZEDCheck the key, its expiry and revocation status. Never put a key in the URL.
409 · QUOTE_NOT_AVAILABLEGet a fresh quote and use a route returned to the same key.
409 · PRICE_CHANGEDThe original minimum could not be protected. Re-quote and review the change.
429 · RATE_LIMITEDWait for Retry-After. Check /usage before requesting another search.
Approval requiredSign only the returned approval, wait for its receipt, then prepare again. Each approval and swap needs its own confirmation.
503 / 504 · Source unavailableUse bounded retries. A partial quote may still contain usable routes; check coverage and source statuses.
SUGGESTIONS / FEEDBACK
A better route
starts with you.
A feature you want. A detail we missed.
Tell us what would make Flowroute better.