PERPETUAL FUTURES24/7 crypto, index and commodity perps
Featured Firm VestVest 5% OFF all plans · from $10 · NQ 50x · no swap fee · USDC payouts on-chain 5% Off Code JMU

RULE CHANGE

Rule Radar

Account streaming

My Funded Perpetuals changed this help center article on November 2, 2026. Updated Neutral

Article adds new price alert event type to streaming API alongside existing account, order, fill, and position events. Four other changes to event structure and deduplication.


What this means

New price_alert event type added with fire_id and alert_id fields; account_id field now only included in account, order, fill, and position events, not all events; deduplication instructions changed to use fire_id for price alerts instead of id; replayed price alert events after since now follow snapshot_end, whereas previously only account/order/fill/position replays were mentioned.

▸ View exact changes
The change in place, line by line
accountupdatedaccountBalance, status, or lockout changed. changes lists the changed fields.
accountremovednoneThe account is no longer reachable with this key.
− Every event also has seq, time (when the service observed the change, in
− epoch milliseconds), and account_id.
+
price_alerttriggeredalertOne of your price alerts fired. See Price alerts.
+ Every event also has seq and time (when the service observed the change,
+ in epoch milliseconds). Account, order, fill, and position events also have
+ account_id.
An order that is placed and finishes before the stream observes it working,
such as a market order that fills immediately, produces its fill and
status when a challenge passes, fails, or closes. balance is the realized balance;
request GET /v1/accounts/{account_id} for equity and rule room.
+ Price alerts
+ A price_alert event fires once each time one of your
+ price alerts triggers, including each fire
+ of a re-armed alert. Alerts belong to your user, so every key you own
+ receives them, including keys limited to certain accounts.
+
FieldMeaning
fire_idUnique per fire. Use it to deduplicate.
alert_idThe alert's id, as in GET /v1/price-alerts/{id}.
alertThe alert as it was when it fired: id, market_id, provider, symbol, coin, price, condition, note, price_source, trigger_price, triggered_at, and status triggered.
+ The event is sent even if the alert was re-armed, edited, or deleted right
+ after it fired.
+ Price alerts are not part of the snapshot. A stream receives the fires from
+ when it connects, and can include one from up to 10 seconds earlier, so
+ deduplicate by fire_id. On a fresh connection with since, fires after
+ since are replayed after snapshot_end. For a longer gap, list
+ GET /v1/price-alerts: triggered alerts show triggered_at, but an alert
+ re-armed since it fired shows only its current state.
Take-profit and stop-loss links
Attached take-profit and stop-loss orders are linked in both directions. When
and closed positions since since, each flagged "replay":true. Replace
your local state with the snapshot; use the replayed events to record what
− happened while you were away. Replayed events can repeat ones you already
− processed just before the disconnect: deduplicate by id.
+ happened while you were away. Price alerts that fired since since follow
+ snapshot_end. Replayed events can repeat ones you already processed just
+ before the disconnect: deduplicate by id (fire_id for price alerts).
snapshot_end then reports replay.complete. Replay reaches back about 100
seconds. If complete is false (you were away longer, or

Every My Funded Perpetuals changeRule Radar: all firms

Scroll to Top