For the complete documentation index, see llms.txt. This page is also available as Markdown.

userFills

Stream live fills of many users from a single connection.

Every live data message includes both routing identifiers with the same value:

{"type": "userFills", "channel": "userFills"}

Other payload fields are omitted above. Existing clients may continue routing on either field.

Subscribe

{ 
    "type": "subscribe",
    "subscription": {
        "type": "userFills",
        "addresses": ["0x742d35Cc6634C0532925a3b844Bc9e7595f7F2e2"],
        "aggregateByTime": true // optional
    }
} 

Unsubscribe

{ 
    "type": "unsubscribe",
    "subscription": {
        "type": "userFills",
        "addresses": ["0x742d35Cc6634C0532925a3b844Bc9e7595f7F2e2"],
        "aggregateByTime": true // optional
    }
}

Fill data format

Each fill contains an address and fill details, fills will be batched per block like:

Reconnection Note: When reconnecting with a session, replay and live events may overlap. Deduplicate using (time, txIndex) - skip fills where this tuple is at or before your last processed fill. See Session Management for details.

Examples

Error messages:

Common errors

Last updated