> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hypedexer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Builder fills

> Every fill routed through one builder code, whatever the user, in Hyperliquid's fill shape plus `twapId`, `cloid`, `builderFee` and `builder`.

Rows come **newest first**: `limit` keeps the newest fills of the window, and `startTime` is only a lower bound (it does not make the result start at `startTime`). There is no cursor: to go further back, narrow the window with `endTime`.

Rows do **not** carry the trader's address. For per-user attribution, use `builderOrderUpdates`, which adds `user` and cursor paging.

**Coverage**: fills from at least July 2026 are returned. The newest fill is typically about a minute old.



## OpenAPI

````yaml /live-data/openapi-rest.json post /info#builderFills
openapi: 3.0.3
info:
  title: 'Hypedexer API: Live Data (REST)'
  version: 0.1.0
  description: >-
    REST API for real-time Hyperliquid market data served from our own
    Hyperliquid nodes.


    All data is accessed through a single unified endpoint `POST /info` that
    dispatches based on the `type` field in the JSON body.


    ## Request types


    | Type | Description | Handled |

    |------|-------------|----------|

    | `metaAndAssetCtxs` | Asset context (funding, OI, prices) | Locally (Redis
    cache) |

    | `allMids` | Mid prices for all coins | Locally (Redis cache) |

    | `userFills` / `userFillsByTime` | Fills for a specific user | Locally
    (volume files) |

    | `allFills` | All fills globally | Locally (volume files) |

    | `trades` | Trade data | Locally (volume files) |

    | `l2Book` / `l2Books` | L2 order book snapshot | Locally |

    | `availableDates` | Available data dates | Locally |

    | `clearinghouseState` | Clearinghouse state, one user (`user`) or many in
    one call (`users`), per dex with `dex` | Locally with upstream proxy per
    user |

    | `openInterestHistory` | Open interest history of a market (~30 s samples,
    with mark price, 24h volume, funding, premium) | Indexed history |

    | `userFunding` / `accountFunding` | Funding payments of a user | Indexed
    history, returned unwrapped |

    | `userNonFundingLedgerUpdates` | Native ledger of a user: deposits,
    withdrawals, transfers, vaults, staking, borrow/lend | Indexed history,
    returned unwrapped |

    | `historicalOrders` | Latest orders of a user with their status | Indexed
    history, returned unwrapped |

    | `userTwapSliceFills` | Fills of a user's TWAP orders with their parent |
    Indexed history, returned unwrapped |

    | `fills` / `recentFills` | Indexed fills with filters (compact shape) |
    Indexed history, returned unwrapped; paging in `X-Has-More` /
    `X-Next-Cursor` headers |

    | `builderFills` / `builderFillsByTime` / `builderOrdersByTime` | Every fill
    or order routed through one builder code | Indexed history |

    | `tpslBook` | Aggregated resting TP/SL trigger orders of a coin, by price |
    Indexed history |

    | `oraclePriceHistory` / `slippageHistory` / `marketLiquidityHistory` |
    Per-market series (~30 to 60 s samples, about 7 days) | Indexed history |

    | `stakingOverview` / `validatorAprHistory` / `globalStakingSummary` |
    Validator snapshots and network staking figures | Indexed history |

    | `liqHistory` | Liquidation events, cursor paging in headers | Indexed
    history |

    | `userTwapStatusesByTime` / `userTwapSummaries` | Status and latest state
    of a user's TWAP orders | Indexed history |

    | `dataCoverage` | Start and latest timestamp per dataset | Indexed history
    |

    | `borrowLendReserveHistory` | Borrow/lend reserve history, one sample per
    minute | Indexed history, returned unwrapped |

    | `meta`, `spotMeta`, `openOrders`, ... | Proxied to local Hyperliquid node
    | Proxied to upstream |


    ## Authentication


    Required. Send your key in the `X-API-Key` header or as `Authorization:
    Bearer <key>`. A request without a valid key returns `401`.


    ## Response format


    Most types return:

    ```json

    { "result": <data>, "cursor": null }

    ```


    `allMids` returns the result directly (not wrapped):

    ```json

    { "BTC": "66764.5", "ETH": "3421.2" }

    ```


    Proxied types return the upstream response as-is.
  contact:
    name: Hypedexer
servers:
  - url: https://api.hypedexer.com
    description: Production, routed to the nearest region (EU or JP)
security:
  - BearerAuth: []
tags:
  - name: Health
    description: Service health and info.
  - name: Asset Context
    description: >-
      Real-time asset context data: funding, open interest, oracle/mark/mid
      prices, volumes.
  - name: Mid Prices
    description: Mid prices for all coins, optionally filtered by DEX.
  - name: Fills
    description: >-
      Executed fills from the Hyperliquid fullnode volumes. Supports
      user-specific and global queries.
  - name: Trades
    description: Trade data from the fullnode volumes.
  - name: Order Book
    description: L2 order book snapshots.
  - name: Metadata
    description: Volume availability and data metadata.
  - name: Clearinghouse
    description: >-
      Clearinghouse state with multi-user support. Each user is fetched
      individually from the upstream Hyperliquid node.
  - name: Proxied Perpetuals
    description: >-
      Perpetual market metadata, margin, OI caps, DEX configs. Proxied to
      upstream Hyperliquid node.
  - name: Proxied Spot
    description: >-
      Spot market metadata, balances, and deploy state. Proxied to upstream
      Hyperliquid node.
  - name: Proxied Trading
    description: >-
      Orders, positions, and active asset data. Proxied to upstream Hyperliquid
      node.
  - name: Proxied Account
    description: >-
      User account info: fees, rate limits, sub-accounts, agents, roles. Proxied
      to upstream Hyperliquid node.
  - name: Proxied Vaults
    description: >-
      Vault summaries, equities, and leaderboards. Proxied to upstream
      Hyperliquid node.
  - name: Proxied Staking
    description: >-
      Delegations, staking summaries, and validator votes. Proxied to upstream
      Hyperliquid node.
  - name: Proxied Exchange
    description: >-
      Exchange status, liquidatable positions, web data. Proxied to upstream
      Hyperliquid node.
  - name: Account History
    description: >-
      Per-address history served from our index, in Hyperliquid's `info` shapes:
      funding payments, native ledger and orders.
  - name: Borrow/Lend
    description: >-
      History of Hyperliquid's borrow/lend reserves, sampled every minute from
      our own node.
  - name: Builders
    description: >-
      Builder-wide feeds: every fill and order routed through one builder code,
      whatever the user.
  - name: Market History
    description: >-
      Per-market series sampled from our own node every 30 to 60 seconds, kept
      about 7 days: open interest, oracle prices, slippage, liquidity.
  - name: Staking
    description: Validator snapshots and network staking figures from our own node.
  - name: Liquidations
    description: Indexed liquidation events with cursor paging.
  - name: Coverage
    description: >-
      What the index holds: per-dataset start and latest timestamp in the region
      answering.
paths:
  /info#builderFills:
    post:
      tags:
        - Builders
      summary: Builder fills
      description: >-
        Every fill routed through one builder code, whatever the user, in
        Hyperliquid's fill shape plus `twapId`, `cloid`, `builderFee` and
        `builder`.


        Rows come **newest first**: `limit` keeps the newest fills of the
        window, and `startTime` is only a lower bound (it does not make the
        result start at `startTime`). There is no cursor: to go further back,
        narrow the window with `endTime`.


        Rows do **not** carry the trader's address. For per-user attribution,
        use `builderOrderUpdates`, which adds `user` and cursor paging.


        **Coverage**: fills from at least July 2026 are returned. The newest
        fill is typically about a minute old.
      operationId: builderFills
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - type
                - builder
              properties:
                type:
                  type: string
                  enum:
                    - builderFills
                builder:
                  type: string
                  description: Builder address (the builder code)
                startTime:
                  type: integer
                  description: Epoch ms, inclusive lower bound. Optional
                endTime:
                  type: integer
                  description: Epoch ms, upper bound
                limit:
                  type: integer
                  minimum: 1
                  maximum: 5000
                  default: 500
            example:
              type: builderFills
              builder: 0x2a2b...0d17
              limit: 2
      responses:
        '200':
          description: Fills through the builder, newest first
          content:
            application/json:
              schema:
                type: array
                items:
                  type: object
                  properties:
                    coin:
                      type: string
                    px:
                      type: string
                    sz:
                      type: string
                    side:
                      type: string
                      enum:
                        - A
                        - B
                    time:
                      type: integer
                      description: Fill time (ms)
                    startPosition:
                      type: string
                    dir:
                      type: string
                    closedPnl:
                      type: string
                    hash:
                      type: string
                    oid:
                      type: integer
                    crossed:
                      type: boolean
                    tid:
                      type: integer
                    fee:
                      type: string
                    feeToken:
                      type: string
                    twapId:
                      type: integer
                      nullable: true
                      description: Parent TWAP, `null` for an ordinary fill
                    cloid:
                      type: string
                      nullable: true
                    builderFee:
                      type: string
                      description: Builder fee paid on this fill
                    builder:
                      type: string
                      description: Builder address
              example:
                - coin: BTC
                  px: '77582'
                  sz: '0.02535'
                  side: A
                  time: 1793449536444
                  startPosition: '0.02535'
                  dir: Close Long
                  closedPnl: '-0.139425'
                  hash: 0xe95e...3b60
                  oid: 591422989327
                  crossed: true
                  tid: 1051160987001703
                  fee: '1.832966'
                  feeToken: USDC
                  twapId: null
                  cloid: 0xa9f2...414d
                  builderFee: '0.983351'
                  builder: 0x2a2b...0d17
        '401':
          $ref: '#/components/responses/Unauthorized'
      security:
        - BearerAuth: []
components:
  responses:
    Unauthorized:
      description: >-
        Missing or invalid API key. The body is `missing api key` or `invalid
        api key`.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            error: Invalid API key
  schemas:
    ErrorResponse:
      type: object
      required:
        - error
      properties:
        error:
          type: string
          description: Error message
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: >-
        Your Hypedexer API key, sent as `Authorization: Bearer <key>`. The
        `X-API-Key: <key>` header and the `api_key` query parameter are accepted
        as well.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.