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

# List RFQ fill history for the authenticated maker or taker



## OpenAPI

````yaml /_generated/openapi.yaml get /query/rfq-fills
openapi: 3.1.0
info:
  title: Joyride Core HTTP API
  version: 0.1.0
  description: |
    HTTP endpoints served by joyride-core v8 components. Decimal money,
    price, and quantity fields are strings with up to 8 decimal places unless
    noted otherwise.
servers:
  - url: https://joyride.exchange/api
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Public
  - name: Query
  - name: Withdrawals
  - name: Market Data
    description: Publicly accessible market data. No authentication required.
  - name: Account
    description: Account-scoped history and provisioning. Requires a bearer JWT.
  - name: Referrals
    description: Referral-code validation and attribution surfaces.
  - name: AI Chat
    description: >
      AI-powered trading assistant. Uses SIWS (Sign In With Solana)
      authentication

      and JWT sessions. Returns responses as Server-Sent Events (SSE).
paths:
  /query/rfq-fills:
    get:
      tags:
        - Query
      summary: List RFQ fill history for the authenticated maker or taker
      operationId: listRfqFills
      parameters:
        - $ref: '#/components/parameters/AccountId'
        - $ref: '#/components/parameters/Limit'
        - $ref: '#/components/parameters/AfterCursor'
        - name: rfq_id
          in: query
          schema:
            $ref: '#/components/schemas/Hex16'
        - name: status
          in: query
          schema:
            type: string
            enum:
              - confirmed
              - finalized
              - reverted
        - name: role
          in: query
          description: >-
            Narrows the participant scope to one role. Default is both. `side`
            on a fill is the taker's, so a consumer describing the caller's own
            trades wants `taker`; a maker reconciling its quotes wants `maker`.
          schema:
            type: string
            enum:
              - taker
              - maker
      responses:
        '200':
          description: RFQ fill rows with an optional continuation cursor
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CursorRows'
        '400':
          $ref: '#/components/responses/QueryError'
        '401':
          $ref: '#/components/responses/QueryError'
components:
  parameters:
    AccountId:
      name: account_id
      in: query
      schema:
        type: integer
        minimum: 0
    Limit:
      name: limit
      in: query
      schema:
        type: integer
        minimum: 1
    AfterCursor:
      name: after
      in: query
      description: >-
        Exclusive keyset cursor returned as next_cursor. Supported by accounts
        and monotone sequence-number lists; unsupported sort orders reject it
        with 400 rather than silently ignoring it. The decimal value must fit
        the backing non-negative PostgreSQL BIGINT; overflow returns 400.
      schema:
        type: string
        pattern: ^[0-9]+$
  schemas:
    Hex16:
      type: string
      pattern: ^[0-9a-fA-F]{32}$
    CursorRows:
      type: object
      required:
        - rows
      properties:
        rows:
          type: array
          items:
            type: object
            additionalProperties: true
        next_cursor:
          type: string
          pattern: ^[0-9]+$
    QueryErrorResponse:
      type: object
      required:
        - error
      properties:
        error:
          type: string
  responses:
    QueryError:
      description: Query API error response
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/QueryErrorResponse'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        SIWS-issued JWT. Admin commands require the `admin` role, `admin:*`, or
        the exact `admin:<type>` scope; admin reads use their documented read
        scope.

````