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. - The Social verification wrappers exist, but those flows need an interactive session. Treat them as non-features for automated trading bots.
- A method that accepts only a session token refuses an API key with
*errors.SessionRequiredError, including guard signer methods,APIKeys.List,APIKeys.Get, andVIP.GetVIPStatus. - Client aliases: 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 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 Go call conventions, context cancellation, and idempotency keys for orders and triggers.