> ## Documentation Index > Fetch the complete documentation index at: https://docs.kalshi.com/llms.txt > Use this file to discover all available pages before exploring further. # Get Historical Orders > Endpoint for getting orders that have been archived to the historical database. API keys restricted to a subaccount return only that subaccount's orders. If supplied, `subaccount` must match the key's restriction. ## OpenAPI ````yaml /openapi.yaml get /historical/orders openapi: 3.0.0 info: title: Kalshi Trade API Manual Endpoints version: 3.34.0 description: >- Manually defined OpenAPI spec for endpoints being migrated to spec-first approach servers: - url: https://external-api.kalshi.com/trade-api/v2 description: Production Trade API server - url: https://api.elections.kalshi.com/trade-api/v2 description: Production shared API server, also supported - url: https://external-api.demo.kalshi.co/trade-api/v2 description: Demo Trade API server - url: https://demo-api.kalshi.co/trade-api/v2 description: Demo shared API server, also supported security: [] tags: - name: api-keys description: API key management endpoints - name: orders description: Order management endpoints - name: order-groups description: Order group management endpoints - name: portfolio description: Portfolio and balance information endpoints - name: communications description: Request-for-quote (RFQ) endpoints - name: multivariate description: Multivariate event collection endpoints - name: exchange description: Exchange status and information endpoints - name: live-data description: Live data endpoints - name: markets description: Market data endpoints - name: milestone description: Milestone endpoints - name: search description: Search and filtering endpoints - name: incentive-programs description: Incentive program endpoints - name: fcm description: FCM member specific endpoints - name: events description: Event endpoints - name: structured-targets description: Structured targets endpoints paths: /historical/orders: get: tags: - historical summary: Get Historical Orders description: > Endpoint for getting orders that have been archived to the historical database. API keys restricted to a subaccount return only that subaccount's orders. If supplied, `subaccount` must match the key's restriction. operationId: GetHistoricalOrders parameters: - $ref: '#/components/parameters/TickerQuery' - $ref: '#/components/parameters/MinTsQuery' - $ref: '#/components/parameters/MaxTsQuery' - $ref: '#/components/parameters/LimitQuery' - $ref: '#/components/parameters/CursorQuery' - $ref: '#/components/parameters/SubaccountQuery' responses: '200': description: Historical orders retrieved successfully content: application/json: schema: $ref: '#/components/schemas/GetOrdersResponse' '400': $ref: '#/components/responses/BadRequestError' '401': $ref: '#/components/responses/UnauthorizedError' '500': $ref: '#/components/responses/InternalServerError' security: - kalshiAccessKey: [] kalshiAccessSignature: [] kalshiAccessTimestamp: [] components: parameters: TickerQuery: name: ticker in: query description: Filter by market ticker schema: type: string x-go-type-skip-optional-pointer: true MinTsQuery: name: min_ts in: query description: Filter items after this Unix timestamp schema: type: integer format: int64 MaxTsQuery: name: max_ts in: query description: Filter items before this Unix timestamp schema: type: integer format: int64 LimitQuery: name: limit in: query description: Number of results per page. Defaults to 100. schema: type: integer format: int64 minimum: 1 maximum: 1000 default: 100 x-oapi-codegen-extra-tags: validate: omitempty,min=1,max=1000 CursorQuery: name: cursor in: query description: >- Pagination cursor. Use the cursor value returned from the previous response to get the next page of results. Leave empty for the first page. schema: type: string x-go-type-skip-optional-pointer: true SubaccountQuery: name: subaccount in: query required: false description: >- Subaccount number (0 for primary, 1-63 for subaccounts). If omitted, defaults to all subaccounts. schema: type: integer minimum: 0 schemas: GetOrdersResponse: type: object required: - orders - cursor properties: orders: type: array items: $ref: '#/components/schemas/Order' cursor: type: string Order: type: object required: - order_id - user_id - client_order_id - ticker - outcome_side - book_side - type - status - yes_price_dollars - no_price_dollars - fill_count_fp - remaining_count_fp - initial_count_fp - taker_fees_dollars - maker_fees_dollars - taker_fill_cost_dollars - maker_fill_cost_dollars properties: order_id: type: string user_id: type: string description: Unique identifier for users client_order_id: type: string ticker: type: string side: type: string enum: - 'yes' - 'no' deprecated: true x-go-type-skip-optional-pointer: true description: > Deprecated. Use `outcome_side` (or `book_side`) instead. See [Order direction](/getting_started/order_direction). This field will not be removed before May 14, 2026. action: type: string enum: - buy - sell deprecated: true x-go-type-skip-optional-pointer: true description: > Deprecated. Use `outcome_side` (or `book_side`) instead. See [Order direction](/getting_started/order_direction). This field will not be removed before May 14, 2026. outcome_side: type: string enum: - 'yes' - 'no' description: > The outcome side this order is positioned for. buy-yes and sell-no produce 'yes'; buy-no and sell-yes produce 'no'. `outcome_side` describes directional exposure only; it does not change the order's price. An order at price `p` with `outcome_side=no` is matched by an order at the same price `p` with `outcome_side=yes` — both parties trade at the same price, just on opposite directions. `outcome_side` and `book_side` will become the canonical way to determine order direction. The legacy `action`, `side`, and `is_yes` fields will be deprecated in a future release — please migrate to these new fields. book_side: $ref: '#/components/schemas/BookSide' description: > Same directional bit as outcome_side in book vocabulary. 'bid' is equivalent to outcome_side 'yes'; 'ask' is equivalent to outcome_side 'no'. `outcome_side` and `book_side` will become the canonical way to determine order direction. The legacy `action`, `side`, and `is_yes` fields will be deprecated in a future release — please migrate to these new fields. type: type: string enum: - limit - market status: $ref: '#/components/schemas/OrderStatus' yes_price_dollars: $ref: '#/components/schemas/FixedPointDollars' description: The yes price for this order in fixed-point dollars no_price_dollars: $ref: '#/components/schemas/FixedPointDollars' description: The no price for this order in fixed-point dollars fill_count_fp: $ref: '#/components/schemas/FixedPointCount' description: >- String representation of the number of contracts that have been filled remaining_count_fp: $ref: '#/components/schemas/FixedPointCount' description: String representation of the remaining contracts for this order initial_count_fp: $ref: '#/components/schemas/FixedPointCount' description: >- String representation of the initial size of the order (contract units) taker_fill_cost_dollars: $ref: '#/components/schemas/FixedPointDollars' description: The cost of filled taker orders in dollars maker_fill_cost_dollars: $ref: '#/components/schemas/FixedPointDollars' description: The cost of filled maker orders in dollars taker_fees_dollars: $ref: '#/components/schemas/FixedPointDollars' description: Fees paid on filled taker contracts, in dollars maker_fees_dollars: $ref: '#/components/schemas/FixedPointDollars' description: Fees paid on filled maker contracts, in dollars expiration_time: type: string format: date-time nullable: true created_time: type: string format: date-time nullable: true x-omitempty: false last_update_time: type: string format: date-time nullable: true x-omitempty: true description: The last update to an order (modify, cancel, fill) self_trade_prevention_type: $ref: '#/components/schemas/SelfTradePreventionType' nullable: true x-omitempty: false order_group_id: type: string nullable: true description: The order group this order is part of cancel_order_on_pause: type: boolean description: >- If this flag is set to true, the order will be canceled if the order is open and trading on the exchange is paused for any reason. subaccount_number: type: integer nullable: true x-omitempty: true description: Subaccount number (0 for primary, 1-63 for subaccounts). exchange_index: allOf: - $ref: '#/components/schemas/ExchangeIndex' x-go-type-skip-optional-pointer: true x-omitempty: false ErrorResponse: type: object properties: code: type: string description: Error code message: type: string description: Human-readable error message details: type: string description: Additional details about the error, if available BookSide: type: string enum: - bid - ask description: >- Side of the book for an order or trade. For event markets, this refers to the YES leg only: `bid` means buy YES, `ask` means sell YES. (Selling YES is economically equivalent to buying NO at `1 - price`, but this endpoint quotes everything from the YES side.) OrderStatus: type: string enum: - resting - canceled - executed description: The status of an order FixedPointDollars: type: string description: >- Fixed-point US dollar string. Most request fields accept 2-4 decimal places (e.g., "0.56", "0.5600"); responses emit up to 6. Valid quote intervals for a given market are constrained by that market's price level structure. example: '0.5600' FixedPointCount: type: string description: >- Fixed-point contract count string (2 decimals, e.g., "10.00"; referred to as "fp" in field names). Requests accept 0-2 decimal places (e.g., "10", "10.0", "10.00"); responses always emit 2 decimals. Fractional contract values (e.g., "2.50") are supported; the minimum granularity is 0.01 contracts. example: '10.00' SelfTradePreventionType: type: string enum: - taker_at_cross - maker description: > The self-trade prevention type for orders. `taker_at_cross` cancels the taker order when it would trade against another order from the same user; execution stops and any partial fills already matched are executed. `maker` cancels the resting maker order and continues matching. ExchangeIndex: type: integer description: Identifier for an exchange shard. example: 0 responses: BadRequestError: description: Bad request - invalid input content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' UnauthorizedError: description: Unauthorized - authentication required content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' InternalServerError: description: Internal server error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' securitySchemes: kalshiAccessKey: type: apiKey in: header name: KALSHI-ACCESS-KEY description: Your API key ID kalshiAccessSignature: type: apiKey in: header name: KALSHI-ACCESS-SIGNATURE description: >- Base64 signature of the pre-sign text (timestamp + method + path) made with the API key's algorithm - RSA-PSS with SHA-256 for RSA keys, Ed25519 for Ed25519 keys kalshiAccessTimestamp: type: apiKey in: header name: KALSHI-ACCESS-TIMESTAMP description: Request timestamp in milliseconds ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.