API reference

The PropExecutor API

What the API gives your firm, what it deliberately does not, and how it fits alongside the admin panel and the executor.

Everything your firm does in the admin panel — provisioning trading accounts, assigning them to traders, handing over executor credentials, watching performance — is available over HTTP. The API exists so you can put those operations behind your own dashboard, your own onboarding flow and your own internal tooling, instead of asking your staff to work in two places.

It is the same tenant data the panel shows, reached with a long-lived scoped key instead of a browser session. There is no separate environment and no sandbox: a key sees your organization’s real accounts, and the accounts it creates are real accounts that spend real credits.

Base URL

One base URL, one version. Every path on these pages is relative to it.

Base URL

https://api.propexecutor.com/v1

Requests are JSON in, JSON out, over HTTPS. Timestamps are RFC 3339 in UTC (2026-09-27T13:45:00Z); the timestamps inside chart series are Unix seconds, which the relevant pages call out.

What you can do with it

Area	What the API gives you
Trading accounts	Provision accounts in bulk, list and filter them, read live balance and equity, assign and reassign a trader, archive.
Analytics	One account's whole performance picture: gain, drawdown, profit factor, Sharpe, hold time, long/short split, and the monthly and yearly P&L tables.
Equity curve	The balance and equity series behind the chart, at whatever resolution the range needs.
Credentials	Read and rotate the Account Number / Server / Password a trader signs into the executor with.
Traders	Create the records accounts hang off, and read a trader's performance across every account they have held.
Rule sets	Define and version the criteria accounts are judged by, and read the rule catalogue your tier unlocks.
Reporting	Firm-wide counts, pass rate, net P&L, a leaderboard, and a feed of every breach and pass.
Webhooks	Be told about breaches and passes within seconds instead of polling for them.
Market data	Instruments, latest prices and OHLC history, for a watchlist or chart of your own.
Billing	Account credits, the ledger behind them, and your purchase history.

What it deliberately is not

Being clear about this saves you building against something that will not arrive. PropExecutor runs your executor and manages the accounts on it. It is not a storefront, and it does not touch your traders.

No trader-facing endpoints. A trader has no account with us, no login and no dashboard here. A trader in this API is a record you create — a name and an email — so an account and its credentials have somewhere to hang. How you recruit, vet, charge and pay traders is entirely yours, outside this platform.
No payments to or from your traders. The only billing relationship is us charging your firm for the platform. There is no endpoint to sell a challenge, and no split-payment plumbing.
No real order routing. Orders are simulated against live market prices. Nothing is ever sent to a broker, an exchange or any venue. See the terms for what that means for what you tell your traders.
No key-creates-key. API keys are issued from the admin panel by a signed-in human, never by the API. A leaked key cannot issue its own replacement.

A first request

Once you have a key (how to get one), this lists your accounts:

GET/v1/accountsAvailablescope · accounts:read

curl

curl https://api.propexecutor.com/v1/accounts \
  -H "Authorization: Bearer pfx_live_YOUR_KEY"

200 OK

{
  "data": [
    {
      "id": "6ab66c2b-a334-ee36-8da4-5f2700000001",
      "account": 10000042,
      "account_type_id": "0f9c…",
      "account_type_name": "$10K Standard",
      "trader_id": "3d21…",
      "trader_email": "trader@example.com",
      "status": "active",
      "status_reason": null,
      "status_changed_at": null,
      "starting_balance": 10000,
      "created_at": "2026-09-14T09:12:04Z"
    }
  ],
  "next_cursor": "MjAyNi0wOS0xNFQwOToxMjowNFrOfDNkMjE"
}

Not every endpoint here is live yet

These docs describe the full surface, which is more than is built today. Every endpoint signature carries an Available or Planned badge, and endpoint availability is the index of which is which — generated from the same catalogue those badges read from, so the two cannot drift.

Build against the available ones now; the planned ones have settled contracts, so you can write your integration before the handler lands.

Accounts are addressed by number

Paths use the 8-digit account number — the one your panel shows and your trader types into the terminal — not the internal UUID. The UUID is still returned as id if you want to store it.

Where to go next

Quickstart — a key, a batch of accounts and one account’s performance, in four requests.
Concepts — what an account type, a rule set and a credit actually are, if you are new to the platform.
Authentication — keys, scopes and how to keep them safe.

Something missing, or an endpoint you need that is not here? Book a call or email info@propexecutor.com.

NextQuickstart