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

builderFills

Stream live fills for a specific builder from a single connection.

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

{"type": "builderFills", "channel": "builderFills"}

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

💧New endpoint - this endpoint is not a part of original Hyperliquid API and is added by us for builder convenience.

Subscribe

{ 
    "type": "subscribe",
    "subscription": {
        "type": "builderFills",
        "builder": "0xb84168cf3be63c6b8dad05ff5d755e97432ff80b",
        "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. One builder holds one venue per connection and aggregateByTime setting; subscribing to it with a different one is rejected (unsubscribe first).

Unsubscribe

{ 
    "type": "unsubscribe",
    "subscription": {
        "type": "builderFills",
        "builder": "0xb84168cf3be63c6b8dad05ff5d755e97432ff80b",
        "aggregateByTime": true // optional
    }
}

Fill data format

Each fill contains an address and fill details of fills by subscribed to builder.

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.

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