Skip to main content
Use this operation when a firm needs to move one account’s daily-loss floor and leave today’s trading result alone. It writes daily_loss_limit_trigger only.
operationId: setDailyLossTrigger A firm API key can call this route for an account in its firm. The operation:
  1. Replaces daily_loss_limit_trigger with the absolute value you send.
  2. Leaves balance, start_of_day_balance, realized_day_pnl, and realized_week_pnl unchanged.
  3. Publishes balance.updated so live risk enforcement uses the new floor.
This is separate from the max-loss cap, which moves the overall trailing floor, and from re-anchor daily loss, which starts a new daily measurement window and zeros today’s realized P&L.

​
Example

An account opened the session at $50,000 with a $1,250 DLL, and is down $250 on the day. You want the floor at $47,500 without wiping that $250 result:

​
Body

​
Response — 200 OK

Confirm the engine is enforcing the new floor with GET /v1/firm-control/accounts/{account_id}/risk-state (daily_loss_limit_trigger).
The firm daily-loss check compares live equity with this trigger. Raising the trigger above current equity breaches the account on the next mark.
The next session roll rebuilds the trigger from the account’s risk-profile daily-loss allowance and the new start-of-day balance. This call changes the floor for the current session. Change daily_loss_value on the account’s risk profile when the new allowance should survive the roll.
This does not unlock an account that already has a daily-loss breach. Move the trigger before the account crosses it, or use the applicable breach-review workflow separately.

​
Errors