NavoSwap
App

HTTP API overview

NavoSwap exposes a versioned JSON API. Typical production base paths look like https://api.navoswap.com/api/v1 (configure your deployment’s public URL; the swap app uses NEXT_PUBLIC_API_URL).

Surface areas

Two API surfaces

Public (no auth)

  • GET /health, GET /assets
  • GET /swap/quote, POST /swap/create
  • GET /swap/status, GET /swap/usd
  • Optional header on create: partner API key for attribution.

Partner (JWT bearer)

  • Authorization: Bearer …
  • Account: signup, sign-in, refresh, profile, 2FA, API keys
  • Ops: orders list, analytics, logout
  • Affiliate: ledger, payouts, webhooks, statements, audit under /partners/affiliate/…

Public swap routes need no login. Partner routes require JWT. Attribution uses x-navoswap-api-key only on create order.

Public swap & assets

  • GET /health: Liveness.
  • GET /assets: Tradable assets (params, networks, maintenance flags).
  • GET /swap/quote: Indicative quote.
  • GET /swap/usd: USD estimate for a from-amount (reference only).
  • POST /swap/create: Create order; optional x-navoswap-api-key.
  • GET /swap/status: Order snapshot.
  • Public analytics may be exposed under /analytics (see deployment).

Partner (JWT)

Routes under /partners/… for signup, email verification, sign-in, refresh, profile, 2FA, API keys, orders, analytics, logout, plus /partners/affiliate/… for balances, ledger, payouts, webhooks, statements, and audit. Send Authorization: Bearer <access_token>.

Next: Swap REST reference · JavaScript SDK · Partner attribution