Overview

How the API is organized, auth model, and the endpoints most teams start with.

XROH abstracts all external liquidity sources behind internal route engines (X1/X2/X3).

Public docs never name third‑party providers or expose their endpoints.

This API exposes provider-agnostic routing. Provider-specific endpoints stay private by design.

Most-used endpoints

Use case

Authenticate requests

Open

Authentication

Use case

Get ranked routes

Open

Quotes API

Use case

Understand failures

Open

Errors and rate limits

Request model

• Send an API key on every request.

• Prefer idempotency for execution-like operations.

• Treat routing and execution as separate phases.

Use quotes for discovery. Only execute after you’ve decided the route.

Response model (client expectations)

• Routes are returned as a ranked list.

• Every route is normalized.

• Clients should handle partial degradation.

What “partial degradation” means:

• some engines can be unavailable

• the API still returns best-effort candidates

• scoring accounts for health and reliability