Skip to main content
SaucerSwap V3 is a central limit order book on Hedera with off-chain matching and on-chain settlement. Professional market makers and bot operators integrate through the Orderbook API: market data is designed to be public (unauthenticated access is rolling out network by network with the July 2026 deployment), while account-scoped trading endpoints sit behind wallet authentication. This page covers how the market works from a maker’s perspective and how to onboard.

​
How the market works

  • Order flow — clients build orders server-side, sign them client-side (EIP-712, with ECDSA and ED25519 key support), and submit them for matching. Settlement happens on-chain through the reactor contract; the on-chain reactor remains the source of truth. See Orders and signing.
  • Fees — fee rates are expressed in pips (1 pip = 1e-6 = 0.0001%), not basis points, and are returned per account and per side by GET /fees/:orderbookId?side=maker. For the taker fee and maker rebate model, see V3 fees.
  • AMM interplay — books can have AMM liquidity routed in (isAMMEnabled), so maker quotes compete with, and are backstopped by, SaucerSwap’s V1 and V2 pools. See How SaucerSwap V3 works.
  • Market data — the order book list, depth snapshots, the public trade tape, and market quotes are public endpoints; live depth diffs and account order events stream over WebSockets. See Market data and WebSockets.

​
Onboarding

1

Read the legal terms and risk notice

Production V3 access requires current acceptance of the terms of service and the V3 order book risk notice, recorded server-side for the applicable access path.
2

Integrate on testnet

Build against https://testnet-orderbook-api.saucerswap.finance first. Work through authentication (wallet challenge and short-lived JWTs), order build, sign, and save, cancellation finality, and WebSocket reconnects. The TypeScript client guide shows a server-side bot shape.
3

Check per-account trading status

GET /onboarding/:orderbookId/status (JWT required) reports whether your account can trade a given market, and GET /fees/:orderbookId returns your effective fee rates per side.
4

Coordinate limits before sustained flow

Production traffic is subject to rate and service-protection limits. Teams planning sustained high-volume traffic should contact [email protected] to coordinate limits and support before ramping up.
5

Move to mainnet

Switch the same flow to https://orderbook-api.saucerswap.finance once your client passes the production checklist: re-authentication on 401, WebSocket reconnects with backoff, snapshot-plus-diff book rebuilds, cancellation reconciliation, and integer-string handling.
Never put a primary wallet private key in a bot process. Use a dedicated integration account, store secrets server-side, and start on testnet before placing mainnet orders.

​
Policy limits

The API applies these limits automatically, as of July 2026: Current limits and error behavior are documented in Limits and errors.

​
Next steps

Orderbook API overview

Endpoint summary, integration flow, and environments for the V3 Orderbook API.

Authentication

Walk through the wallet challenge flow and JWT handling for protected endpoints.

TypeScript client

Study a server-side bot client shape covering build, sign, save, and cancel.

V3 fees

Understand the taker fee and maker rebate model and how fee rates are quoted in pips.