API URLs
Build Surface Map
Each Build page starts with a surface map: use it to choose the REST route family, TypeScript SDK namespace, live WebSocket channel, or gRPC service for the action on that page.SDKs
Official SDKs handle Monaco auth, request signing, request formatting, and trading workflows. Generated clients expose typed REST or gRPC clients for other languages.TypeScript
Build authenticated clients, sign requests, place and cancel orders, query markets and profiles, manage vault flows, and subscribe to live feeds.
RESTWebSocketReact
Provider and hooks for wallet login, live orderbooks and trades, user balances, positions, orders, fees, and vault actions in React apps.
RESTWebSocketRust
Backend clients for authenticated REST and gRPC integrations, including request signing, order management, account data, and market data.
RESTgRPCOther languages
Generate typed REST or gRPC clients from Monaco’s published protobuf files for Go, Python, Java, C++, and other backend languages. Start with Python, Go, C++ & More or the Buf registry.Authentication
Public market data can be read without a user session. Trading, account, deposit, withdrawal, and other user-specific routes require an authenticated wallet session. SDKs handle session creation, request signing, and session refresh. Direct integrations sign each request with a session key: over REST follow the REST authentication flow, and over gRPC follow authenticated gRPC (metadata names, canonical signing string, and a runnable signed example). See Wallets & Auth for Sei network, gas, wallet setup, and asset IDs.Private alpha requirementsAuthenticated requests require a Monaco client ID. Email [email protected] to get one.
APIs
Applications require different connection patterns. REST is the most compatible request/response interface, WebSockets are for live market and account events, and gRPC is the typed low-latency path for backend services. Choose based on your infrastructure, tooling, and latency requirements.REST API
Standard HTTP/JSON access to Monaco routes for market data, account state, orders, deposits, withdrawals, and admin workflows. Use it when you want broad tooling support, predictable request/response calls, or OpenAPI-based clients.
Most compatible and standardWebSocket API
Configurable live subscriptions for Monaco events: all trades, orderbook updates, candles, and authenticated streams for your own orders, balances, positions, and liquidation risk. Use it when your UI or service needs data pushed as markets move.
Best for listening to datagRPC API
Strongly typed HTTP/2 services for backend systems that need fast order entry, account queries, market data, and generated clients from Monaco protobuf contracts. Use it when latency and typed service contracts matter more than generic HTTP tooling.
Fastest for trading quickly