> ## Documentation Index > Fetch the complete documentation index at: https://docs.rook.pm/llms.txt > Use this file to discover all available pages before exploring further. # Get fee schedules > Look up published venue fee rules applicable to selected Rook listings. Omit effective_at for current rules or provide a UTC timestamp for an available historical schedule. Results identify schedule/version, effective periods, currency, formula and required account inputs where known. Unsupported or unknown schedules are explicit; a missing fee is never assumed to be zero. Account tier, rebates or discounts may require information outside this API. A schedule provides evaluation context without promising a final account-specific execution cost. See the [integration guide](/guides/market-data) for the workflow and interpretation of this response. ## OpenAPI ````yaml GET /fee-schedules openapi: 3.1.0 info: title: Rook API version: 0.1.0-design description: Markets, settlement relationships, scenarios, payouts and market data. servers: - url: https://api.rook.pm/v1 description: Proposed API origin; not an assertion these operations are callable. security: - ApiKeyBearer: [] tags: - name: Reference data description: Events, unified markets and native-ID resolution. - name: Families and scenarios description: Family scope and versioned scenario columns. - name: Relationships and Combos description: Related-market discovery, selected-set inference and Combo interpretation. - name: Payouts and exposure description: Scoped per-unit payouts and stateless portfolio/candidate calculations. - name: Market data description: Current prices, history, L2 books, prints, statistics and published fees. - name: Fair values description: Future private customer estimates; not Rook forecasts. - name: Coverage and updates description: Supported capabilities and incremental semantic changes. paths: /fee-schedules: get: tags: - Market data summary: Get fee schedules description: >- Look up published venue fee rules applicable to selected Rook listings. Omit effective_at for current rules or provide a UTC timestamp for an available historical schedule. Results identify schedule/version, effective periods, currency, formula and required account inputs where known. Unsupported or unknown schedules are explicit; a missing fee is never assumed to be zero. Account tier, rebates or discounts may require information outside this API. A schedule provides evaluation context without promising a final account-specific execution cost. operationId: getFeeSchedules parameters: - name: listing_ids in: query required: true description: >- Rook listing IDs from /markets or /markets:resolve. Select the venue and outcome side explicitly; repeat the query parameter for multiple listings. schema: type: array items: type: string description: Opaque text identifier. Preserve its exact value. minLength: 1 minItems: 1 style: form explode: true example: - lst_pm_fed_dec_2026_cut_yes - name: effective_at in: query required: false description: >- UTC time at which a fee schedule must apply. Omit for the current applicable schedule; unavailable historical rules are explicit. schema: type: string format: date-time - name: X-Client-Request-Id in: header required: false schema: type: string description: Caller correlation reference; not an idempotency guarantee. responses: '200': description: Success. content: application/json: schema: $ref: '#/components/schemas/GetFeeSchedulesResponse' example: items: - listing_id: lst_pm_fed_dec_2026_cut_yes status: UNAVAILABLE schedule_id: null version: null currency: USDC required_account_inputs: [] reason: >- No verified fee schedule is available for this illustrative listing. Fees must not be assumed to be zero. next_page_token: null snapshot_id: snap_rates_20261019_120000 as_of: '2026-10-19T12:00:00Z' headers: X-Request-Id: description: Server request trace ID. schema: type: string description: Opaque text identifier. Preserve its exact value. minLength: 1 components: schemas: GetFeeSchedulesResponse: type: object properties: items: type: array items: $ref: '#/components/schemas/FeeSchedule' next_page_token: type: 'null' description: >- All requested IDs are accounted for in one bounded batch; no silent truncation. snapshot_id: type: string description: Opaque text identifier. Preserve its exact value. minLength: 1 as_of: type: string format: date-time required: - items - next_page_token - snapshot_id - as_of additionalProperties: true FeeSchedule: type: object properties: listing_id: type: string minLength: 1 description: >- Rook ID for one outcome listing on one venue; preserves venue provenance. schedule_id: anyOf: - type: string description: Opaque text identifier. Preserve its exact value. minLength: 1 - type: 'null' version: anyOf: - type: string description: Opaque text identifier. Preserve its exact value. minLength: 1 - type: 'null' status: type: string enum: - KNOWN - ACCOUNT_DEPENDENT - UNAVAILABLE currency: anyOf: - type: string - type: 'null' maker_formula: anyOf: - type: string - type: 'null' taker_formula: anyOf: - type: string - type: 'null' parameters: type: array items: type: object properties: name: type: string value: $ref: '#/components/schemas/Decimal' required: - name - value additionalProperties: false rounding: anyOf: - type: string - type: 'null' minimum: anyOf: - $ref: '#/components/schemas/Decimal' - type: 'null' cap: anyOf: - $ref: '#/components/schemas/Decimal' - type: 'null' effective_from: anyOf: - type: string format: date-time - type: 'null' effective_until: anyOf: - type: string format: date-time - type: 'null' required_account_inputs: type: array items: type: string source_url: anyOf: - type: string format: uri - type: 'null' reason: anyOf: - type: string - type: 'null' required: - listing_id - status - schedule_id - version - required_account_inputs additionalProperties: true Decimal: type: string description: >- Exact base-10 value encoded as a string; no exponent or non-finite values. pattern: ^-?(0|[1-9][0-9]*)(\.[0-9]+)?$ securitySchemes: ApiKeyBearer: type: http scheme: bearer description: >- Proposed server-to-server API key. No client request HMAC signing scheme is specified. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.