Setup Guide
Choose your integration path and follow the setup for your layer. See the Packages overview for installation, package descriptions, and peer dependencies.Need sign-in flows? Start with Authentication. For wire-level streaming details,
see WebSocket Protocol. For end-to-end implementations, see
Real-Time Orderbook and
Real-Time Charts. For theming and partner branding, see
Customize UI.
- SDK (vanilla JS/TS)
- React (hooks)
- React (UI components)
- React (with auth)
No framework dependency. Works in browsers, Node.js, and React Native.
WebSocket endpoint
If you create raw sockets yourself, connect to:Testing mode limits
All new partner apps start in testing mode — a sandboxed state that lets you build and verify your integration without committing to the full live-mode agreement. Two hard caps apply while an app is in testing mode:Existing users can always sign in — the user cap only blocks new account creation once the
limit is reached. No data is lost when the cap is hit.
How the limits work
When a new user tries to sign in and the app has already registered 20 users, the sign-in endpoint (POST /auth/verify) returns a 403 with a plain-language message explaining the
situation. Likewise, when a new trade is submitted after 100 trades have been placed, the
execution endpoint returns a 403. Both error responses use the message field of the standard
{ message: string } error body — you can surface this text directly in your UI without any
special-casing.
message query
parameter on the redirect URL (alongside an error=testing_user_limit_reached param your
frontend can key off).
Lifting the limits — signing the partner agreement
Once you are ready to go live, sign the partner agreement from the admin dashboard (Apps → your app → Go Live). Signing setspartnerAgreementSigned = true on your app and
immediately removes both caps — no restart or config change needed. The agreement is a one-time
action; it cannot be reversed from the dashboard.
After signing:
- New users can sign in without restriction.
- New trades can be placed without restriction.
- Existing testing-mode users and trades are preserved; the historical counts are not reset.
Next steps
Authentication
Add wallet, OAuth, or email sign-in on top of the base client setup.
WebSocket Protocol
Review the wire format, auth upgrade flow, heartbeat, and reconnection behavior.
Real-Time Orderbook
SDK, hooks, and UI recipes for live orderbook rendering.
Real-Time Charts
Build live OHLCV charts from REST history and WebSocket updates.
Customize UI
Brand AGG components with CSS variables, labels, formatting, and slots.