/v1/firm-control
Per-account lock, flatten, cancel, and live order/position reads use the same firm API key on /v1/accounts and /v1/orders. See Per-account trading control.
What you can do
Provision accounts
Bridge to the Trading API — onboard a trader and create one or more evaluation accounts.
Embed the terminal
Mint iframe sessions so traders trade inside your website without a separate Tradara login.
Manage staff & RBAC
Invite operators, assign roles, define custom roles, and apply per-staff permission overrides.
Mint API keys
Create, rotate, and revoke
tdr_live_ / tdr_test_ keys for your integrations.Configure webhooks
Get order, fill, account, and trade events pushed to your service.
Emergency halt
Stop all trading firm-wide and inspect the resulting job state.
Per-account trading
Lock, flatten, cancel, and read live orders and positions for one account.
Adjust balance
Deposit or withdraw cash on an account (payouts and admin credits).
Max loss limit
Set max-drawdown mode, allowance, and trailing cap for an account.
Reconciliation
Preview and run end-of-session reconciliation against your books.
Authentication
All Prop Firm API routes accept:- Firm API key —
X-Tradara-Api-Key: tdr_live_.... The gateway auto-injectsX-Firm-ID. - Staff JWT —
Authorization: Bearer <jwt>. JWTs that belong to multiple firms must sendX-Firm-IDexplicitly.
/v1/firm-control/me/* are JWT-only (terminal onboarding) and not callable with firm API keys. See Terminal onboarding (JWT).
Endpoint groups
Read-only backoffice queries
For low-volume aggregate reads (dashboards, scheduled exports), prefer the projection-backed/v1/admin/query/* routes. They scale across many accounts but lag the live stream by seconds. For one account right now, use Read orders and positions.
