The user feed streams your account‑scoped updates (orders, fills, cancels).Documentation Index
Fetch the complete documentation index at: https://docs.4casters.io/llms.txt
Use this file to discover all available pages before exploring further.
Messages
The user feed sends each update as a bare JSON object (no tuple envelope). All updates share one envelope; the action is determined by which ofunmatched / matched are populated and by origin.
Common envelope
messageID is the Redis stream entry id added by the streaming-api before send. After a reconnect, replay anything you missed via GET /v2/user/messages?afterID=<lastMessageID>.
How to identify the action
unmatched.filled === 0 && unmatched.offered > 0-> order placedunmatched.offered === 0-> order cancelledmatched != null && unmatched == null-> matched as takermatched != null && unmatched != null-> matched as maker (partial fill ifunmatched.remaining > 0)
Action: order placed
A new offer was put on the book.unmatched.filled is 0, unmatched.offered > 0, and matched is null.
Action: order cancelled
The user (or the system on their behalf) cancelled an offer. The distinguishing field isunmatched.offered === 0.
Action: order matched (taker)
The user took someone else’s offer.unmatched is null, matched carries the fill, and origin is "wager".
Action: order matched (maker, partial fill)
Someone hit the user’s posted offer. Bothmatched and unmatched are populated; unmatched.remaining shows what is still on the book. Because unmatched is set, origin is "offer".