Skip to main content
The developer API is in beta. Breaking changes may be introduced at any time.

Trading coverage

The public API can place and manage trades on existing challenge accounts. It uses the website’s paper execution engine and server-side trading rules. It does not expose every website feature. See Trading with the API for behavior and examples and the REST reference for request and response fields.

Features that require the website

The public REST contract has no endpoints for these website capabilities:
  • Signup and onboarding, challenge purchases, identity verification, agreements, payout requests, and billing or purchase-history management.
  • API-key creation and management or sandbox-account creation and reset.
  • Saved trading preferences, watchlists, and notifications.
  • Journal notes and tags, performance dashboards, and account equity-history charts.
Existing copy-trading configurations still apply when an API request trades a lead account. Inspect those groups through the API or on the website before running an automated strategy. The API lists only groups whose lead and every follower your credential can access, and saving never changes groups it does not list. Followers remain subject to the same manual-trading restrictions as in the terminal. Browser-internal connections are not an API-key subscription contract. REST reads return snapshots; for pushed changes on your accounts, use the account stream instead of polling. Use bounded reconciliation and respect the shared request budgets.

MCP and CLI coverage

The REST methods in the MCP server and CLI are derived from the REST specification. They do not add website capabilities missing from REST. MCP exposes the REST read and trading operations as tools. The REST specification also contains two CLI authentication endpoints that MCP does not expose as tools. Consult the endpoint reference for the currently available fields and filters. Live MCP access uses browser OAuth. Direct REST calls use an API key, while CLI login can create a browser-approved session. Sandbox MCP calls accept a test API key. See Authentication and Sandbox.