Revert Breach

curl --request POST \
  --url https://api.{your-broker}.slate-labs.com/prop/breach-events/{breach_id}/revert \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "reason": "<string>"
}
'

{}

Prop trading

Revert Breach

Revert a breach event decision and REOPEN the account (REVERT-1 / E-010).

A wrongful breach is undone in ONE transaction by exactly mirror-reversing the breach_handler’s terminal-breach mutations:

breach_events.review_status -> ‘reverted’;
prop_account_state -> status=‘active’, clear breached_at / breached_rule_type / breached_event_id (only when THIS breach is the one that breached the account — breached_event_id = :bid);
trading_accounts.close_only -> FALSE (so the order-worker lets the trader open positions again);
prop_journeys -> back to ‘active’ IF the breach-journey consumer flipped it to ‘completed’ for this journey (LIFE-1) and it isn’t otherwise terminal;
emit prop.state.invalidate so the order-worker prop-breach engine reloads the now-active state.

Idempotent: reverting an already-reverted breach is a no-op (returns unchanged).

POST

prop

breach-events

{breach_id}

revert

Revert Breach

curl --request POST \
  --url https://api.{your-broker}.slate-labs.com/prop/breach-events/{breach_id}/revert \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "reason": "<string>"
}
'

{}

Authorizations

Authorization

string

header

required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

breach_id

string<uuid>

required

Body

application/json

reason

string

required

Required string length: 1 - 500

Response

Successful Response

The response is of type Response Revert Breach Prop Breach Events Breach Id Revert Post · object.

Approve Breach List Journeys