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, platform price alerts, 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. Configure and inspect those groups on the website before running an automated strategy. 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; use bounded reconciliation and respect the shared request budgets.

​
MCP, CLI, and SDK coverage

The REST methods in the MCP server, CLI, and SDKs are derived from the REST specification. They do not add website capabilities missing from REST. The SDKs also provide price streaming through the dedicated public market WebSocket feed. 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.

​
MyFundedPerps SDK names

The SDKs use the MyFundedPerps brand across package names and imports: These SDKs are currently maintained in the project repository and have not been published to public package registries. The homepage examples use these names; registry installation commands will be available when the packages are published.