This page is about the Solana routes. The EVM routes (
/evm/…) answer in the same shape, {"error", "reason"}, without quoteId, with their own reasons: see EVM errors.error code, a reason, and the quoteId of the request when it got one (except 405 and 413, which come from the HTTP layer without a JSON body):
Two error bodies differ from the shape above:
not_readycarries a list,reasons, instead ofreason;low_liquidityaddsliquidity: {venue, hubMint, hubAmount}, the deepest pool the router found.
quoteId is absent when the body or query could not be parsed, on an unknown path and on every POST /tx/v1 error. A failed build gets a new quoteId, not the quote’s.
Quote declines
Build declines
A build without
quoteResponse or routeTicket quotes first, so it can also answer every quote decline with the same status, except cold_unresolved and the cold-mint 503s.
A build decline’s reason is a short label; the detail is in the router’s log, under the same quoteId.
/ready
GET /ready is 200 {"ready": true, "reasons": []} when the router can quote and build, and 503 with every reason it cannot otherwise. Use it for your load balancer’s health check; GET /health only says the process is up.
The last four are present only when they have something to say: a healthy router answers just
{"ready": true, "reasons": []}.
What keeps a router red: no account stream yet, the index not built, your swap deploy’s config unreadable or missing, the token directory not being written, a stalled stream or a stalled re-read, more than 1% of quote tapes or fills dropped. A paused config is not a readiness reason: the router stays ready and every build answers 503 swap is paused on chain.
On a fresh install the router knows only the tokens traded since it started. A long-tail token never seen gives
422 cold_unresolved on its first quote, until its first trade arrives or the background pool search finds it.