Skip to main content
The Hyperprop Platform API lets your firm provision evaluation and funded trading accounts, manage traders and plans, react to account lifecycle events via signed webhooks, and reconcile billing — all programmatically, from your own backend.

Quickstart

Create your first trading account in three requests.

Authentication

API keys for your backend, Bearer tokens for user sessions.

Webhooks

Signed account lifecycle events, with retries and redelivery.

Partner integrations

Trade on behalf of a trader with a key they control.

API reference

Platform and Trade — each generated from its live OpenAPI spec.

​
Services & base URLs

The public API is two services behind one domain. Each has its own base URL, its own auth model, and its own section in the API reference:
  • The Platform API is the firm-facing control plane: accounts, plans, rules, traders, billing, webhooks. This is where prop firm backends live. Approved partner apps can also read a trader’s journal here.
  • The Trade API is the trading engine itself: orders, positions, brackets, risk settings, copy trading. Called on behalf of a trader — either by Hyperprop’s own apps, or by a registered third-party app using a partner session.
All documented paths in each tab are relative to that service’s base — for example GET /v1/organization/trading-accounts on the Platform API is https://api.hyperprop.com/platform/v1/organization/trading-accounts.

​
Browser access policy

This section is about where a request may originate from in a browser — it is not a statement about who may integrate. Server-to-server access to every service below is available through the documented auth methods. CORS and WebSocket origins are restricted as follows:
  • Open to any web origin: Platform API organization endpoints, MCP, and these docs’ specs. Call them from your backend or your own dashboard freely.
  • Hyperprop first-party only: the Trade API and every Platform API endpoint outside the organization API. Browsers can call these only from Hyperprop’s own apps.
This only affects browsers — server-to-server calls and native apps don’t send an Origin header and are unaffected. A registered partner app calling the Trade API from its own backend is unaffected by this policy; see Partner integrations. Building a trader-facing web frontend that needs direct Trade API access? Contact us to have your origin approved; it’s a configuration change, not a code change, on our side.

​
Real-time channels

​
Platform API sections

Every section except Partner access uses your organization API key.

​
How the pieces fit

  1. Plans define what you sell (starting balance, price metadata).
  2. Rules define how an account is evaluated (loss limits, drawdown mode, profit target, consistency, permissions).
  3. Trading accounts are instances of a plan+rule assigned to a trader.
  4. The trade engine enforces the rules in real time; when an account passes, fails, or changes in any way you care about, a webhook tells your backend.
  5. Purchases, payouts, and billing endpoints close the loop for reconciliation.

​
AI agents

The platform ships a built-in MCP server so AI assistants can operate your organization through the same API, with the same permissions and audit logging. See the MCP connector guide.