Run accounts for your firm - trdrs Engine API

This is the short tour. Everything runs with your partner key against /api/partner/ routes, and reaches only accounts your firm issued. Traders never appear on this surface — they sign up and trade in the app; you issue and govern the accounts they trade. Each step below is one call and one link. The linked guide carries the detail: the item semantics, the units, the refusals, the audit trail.

Issue evaluation accounts

Up to 20 in one call. Each item names the trader by their trdrs sign-in email, a startingBalance in whole dollars, and your own referenceId.

curl -X POST "$TRDRS_API_BASE_URL/api/partner/accounts" \
  -H "Authorization: Bearer $TRDRS_PARTNER_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "accounts": [
      { "email": "trader@example.com", "startingBalance": 50000, "referenceId": "order-84117" }
    ]
  }'

The batch answers item by item, in order, so one unknown email fails its own item and nothing else. → Issue evaluation accounts

Set the account's risk controls

Five controls in one write: daily and weekly loss, daily and weekly profit, and an end-of-day close. Enforcement is live from the write — a control that fires flattens and locks the account.

curl -X PUT "$TRDRS_API_BASE_URL/api/partner/accounts/risk" \
  -H "Authorization: Bearer $TRDRS_PARTNER_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "accountNumber": "EVAL-7C21A9",
    "dailyLossEnabled": true,  "dailyLossValue": 1000,
    "weeklyLossEnabled": true, "weeklyLossValue": 3000,
    "eodCloseEnabled": true,   "eodCloseValue": 15
  }'

→ Govern account risk

Halt, resume, and reset

Halt trading stops new orders on one account without closing anything; resume clears your own halt and only your own. Reset an issued account returns an evaluation to its starting state and clears its positions and working orders.→ Govern account risk

Record a balance operation

A payout, a promotional credit, a correction — money that moves without a trade, written to the ledger first and keyed on your referenceId so it can never happen twice.

curl -X POST "$TRDRS_API_BASE_URL/api/partner/balance-op" \
  -H "Authorization: Bearer $TRDRS_PARTNER_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "accountNumber": "EVAL-7C21A9",
    "op": "debit",
    "amount": 800,
    "referenceId": "payout-2026-08-31-a"
  }'

→ Record balance operations

Read the meter

Get monthly usage and List billed accounts are your reconciliation views — the same numbers your invoice is built from, from the same query.

curl "$TRDRS_API_BASE_URL/api/partner/usage" \
  -H "Authorization: Bearer $TRDRS_PARTNER_KEY"

→ Read your usage

Stop polling

Register an https endpoint and the platform POSTs account.reset, balance.recorded, risk.locked and risk.unlocked to it as they happen.→ Receive events

One thing to know before you start

Every route in this group is served where the deployment runs the prop engine. Where it does not, they all answer 404 — so a 404 on your very first call is a deployment question, not a bug in your request.

Where to go deeper

Issue evaluation accounts — the batch shape, the per-item results, and what balance means.
Govern account risk — the five controls, and halt versus resume versus reset.
Record balance operations — payouts, credits, and their audit trail.
Read your usage — what the meter counts, and how to reconcile an invoice.
Prop firms — the whole firm surface in one page.

​One thing to know before you start

​Where to go deeper

One thing to know before you start

Where to go deeper