Python, Go, and Rust are API-key SDKs. They share the ConnectRPC + WebSocket Protobuf trading surface. They do not replace the TypeScript browser client.
Not available here
| Capability | Use instead |
|---|---|
| Wallet / browser login | TypeScript SDK |
| Session MFA enrollment / challenges | TypeScript SDK |
| Account resolve / lookup | TypeScript / session clients |
| SBE WebSocket | SBE getting started |
| FIX Classic / FIX-SBE | FIX Classic, FIX-SBE |
Subaccount MFA requirement flags (policy) may still appear on API-key policy APIs, that is not the same as performing MFA challenges in this SDK.
Easy to miss
- On-chain Funding → Trading and Funding → external via the
chainmodule (not ConnectRPC). See Deposits & withdrawals. - Collaboration wrappers (polychart / layout / whiteboard / social verification) may appear in the client tree, but live API-key access is limited: whiteboard and social verification are JWT/session-only, and some layout/polychart endpoints may be unmounted. Treat them as non-features for automated trading bots. Thin reference pages exist for discovery only.
- Client aliases and sync/async differences, see Architecture.
Capability matrix
Compare languages: SDK capability matrix.
Transports: connectivity matrix.
Related Topics
Architecture How the API-key SDK layers ConnectRPC, realtime, catalogs, and services. Environments Default testnet endpoints and how to point the client at another deployment. Authentication model Ed25519 API-key request signing for ConnectRPC and private realtime channels. Catalog & precision Spot/Zipper catalogs, decimal strings, and scaled-integer inputs. Requests & idempotency How Python SDK calls are shaped, cancelled, retried, and reconciled with client order ids and request ids.