Create a sandbox API key and validate the same SDK methods and workflows you will use in production, backed by generated test data.
Use the client or server SDK to open a customizable portal where each user can authenticate and connect a supported brokerage.
Read accounts, orders, positions, and balances through a consistent response model, then add trading with a unified order workflow.
Give users a consistent, brand-aligned portal instead of designing and maintaining a separate onboarding flow for every brokerage.
Use a common model for accounts, orders, positions, and balances so downstream product logic is not tied to each broker's schema.
Add supported institutions and trading capabilities through the same integration rather than introducing another broker-specific stack.
Choose a client-side TypeScript SDK or server-side TypeScript and Python SDKs, with consistent concepts across environments.
Use generated sandbox data to test account, order, position, and balance workflows before connecting production broker accounts.
Follow the quick start, inspect method-level API references, and try SDK calls in the interactive playground.