get_accountsGet all brokerage accounts for the user and link new ones.
View operation →One API connects your product to your users’ brokerages. Read their holdings, create orders, and execute the trades they approve—all inside the experience you design.
Use the same request shape across the account and trading operations. Your application controls the experience; Trade It handles the brokerage integration.
get_accountsGet all brokerage accounts for the user and link new ones.
View operation →get_holdingsGet holdings for a brokerage account.
View operation →get_tradesGet the user's recent trades with cursor pagination.
View operation →create_tradeCreate a trade order for user to review.
View operation →create_options_tradeCreate an options trade order with one or more legs (spreads, single options, etc.).
View operation →execute_tradeExecute a draft trade order.
View operation →cancel_tradeCancel a draft or cancellable brokerage order.
View operation →Use an API key for your own workflows. Use per-user OAuth for a platform, with scoped access to each user’s connected brokerage accounts.
API keys, access tokens, refresh tokens, and your client secret stay on your server. Every request runs in the authorized user’s context.
POST /api/tool/execute
Authorization: Bearer <token_or_api_key>
Content-Type: application/json
{
"toolName": "get_accounts",
"params": {}
}Keep order creation and execution separate. Show the returned details, ask for approval, then submit that draft and follow its status.
Read connected accounts and their brokerage capabilities.
Create a stock, crypto, or options order with the user’s instructions.
Present the specific account, action, amount, price, and legs for approval.
Execute the approved draft, read updated order state, or request cancellation.
No. The API works without an embedded modal. You can build your own account views and order review interface, or combine direct API calls with the SDK connection portal.
Holdings are cached daily by default. Eligible paid plans and partner-linked users can request a refresh, subject to a one-minute cooldown per connected account. Use returned timestamps and order state to show data freshness.
After an MCP or API 401, start the OAuth authorization flow using the published authentication guide. Alternatively, the user can create an API key from their Trade It account. Both paths provide bearer-token authentication.
Draft-first is the recommended flow. An account configured for automatic execution may return an already submitted trade from a create call. Inspect the returned status and never assume an order is still a draft.
https://tradeit.app/openapi.jsonBring brokerage data and approved execution into your investing product.
Start your integration