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"],
"venue": "skew", // optional
"aggregateByTime": true // optional
}
} venue (optional) delivers only fills on outcome markets deployed by that permissionless venue, e.g. "skew": 2–4 ASCII letters, case-insensitive. An unknown venue delivers nothing. A connection holds one venue per aggregateByTime setting; subscribing with a different one is rejected (unsubscribe first).
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:
Outcome (#NNNN) fills whose market was deployed on a HIP-4 venue also carry venue (e.g. "out"). The field is omitted for validator-deployed outcomes and all other coins.
Examples
Error messages:
Common errors
Last updated