Skip to main content
OceanX exposes two read-only Router endpoints: one requests the route the engine would use, and one reads the status of an already-submitted Solana transaction. Neither endpoint builds, signs, or submits a transaction. Both require the md.read scope. POST /route costs 1 against the quote budget; GET /status/{id} uses the standard REST budget.

Request a route

POST /api/v1/route
The MVP route endpoint is Solana-only and uses OceanX Raptor. It accepts JSON and returns the current quote object selected by the engine. The response has the same route, amount, impact, slot, venue and timing fields documented for GET /spot/quote.

Body

Request

For the successful response fields, see the verified /spot/quote response. A pair or size with no route returns 404 no_route. Validation failures return 400 invalid_request.
A route is a read-only quote, not a transaction or a guarantee of execution. There is no public build, sign, or execute endpoint. Never treat a quote id as proof that a transaction was submitted.

Read transaction status

GET /api/v1/status/{id}
Looks up the public status of an already-submitted Solana transaction. id must be a valid 64-byte base58 Solana transaction signature.
An invalid signature returns 400 invalid_signature; a valid signature for which no public status is available returns 404 status_not_found. The endpoint does not submit, retry, or alter the transaction.

Authentication error example

Requests without a key return the standard API error envelope:
Responses are JSON, Cache-Control: no-store, and CORS-enabled. Upstream availability failures use a 503 upstream_* error rather than returning a stale or invented quote/status.