---
title: "Get Order"
method: GET
path: "/portfolio/orders/{order_id}"
tags: ["orders"]
---

# Get Order

`GET /portfolio/orders/{order_id}`

## Request

- Base URL: `https://external-api.kalshi.com/trade-api/v2`
- URL: `https://external-api.kalshi.com/trade-api/v2/portfolio/orders/{order_id}`
- Auth: API key in header `KALSHI-ACCESS-KEY` and API key in header `KALSHI-ACCESS-SIGNATURE` and API key in header `KALSHI-ACCESS-TIMESTAMP`

Endpoint for getting a single order.

## Path parameters

- `order_id` string, required

## Response `200`

Order retrieved successfully

- GetOrderResponse
  - `order` Order, required
    - `order_id` string, required
    - `user_id` string, required: Unique identifier for users
    - `client_order_id` string, required
    - `ticker` string, required
    - `side` 'yes' | 'no': 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` 'buy' | 'sell': 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` 'yes' | 'no', required: 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` 'bid' | 'ask', required: 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.)
    - `type` 'limit' | 'market', required
    - `status` 'resting' | 'canceled' | 'executed', required: The status of an order
    - `yes_price_dollars` string, required: 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.
    - `no_price_dollars` string, required: 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.
    - `fill_count_fp` string, required: 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.
    - `remaining_count_fp` string, required: 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.
    - `initial_count_fp` string, required: 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.
    - `taker_fill_cost_dollars` string, required: 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.
    - `maker_fill_cost_dollars` string, required: 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.
    - `taker_fees_dollars` string, required: 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.
    - `maker_fees_dollars` string, required: 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.
    - `expiration_time` string, date-time, nullable
    - `created_time` string, date-time, nullable
    - `last_update_time` string, date-time, nullable: The last update to an order (modify, cancel, fill)
    - `self_trade_prevention_type` 'taker_at_cross' | 'maker': 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.
    - `order_group_id` string, nullable: The order group this order is part of
    - `cancel_order_on_pause` boolean: 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` integer, nullable: Subaccount number (0 for primary, 1-63 for subaccounts).
    - `exchange_index` integer: Identifier for an exchange shard.

## Other responses

- `401`: Unauthorized - authentication required
- `404`: Resource not found
- `500`: Internal server error

## Changes

- **2026-07-31** `a07481be8bf9`: 3 warning
  - removed the optional property `service` from the response with the `401` status
  - removed the optional property `service` from the response with the `404` status
  - removed the optional property `service` from the response with the `500` status
- **2026-07-13** `a671b3e77f35`: 2 breaking
  - the response property `order/action` became optional for the status `200`
  - the response property `order/side` became optional for the status `200`
- **2026-05-18** `7e31fc4590e0`: 5 info
  - added the optional property `order/exchange_index` to the response with the `200` status
  - response property `order/action` deprecated
  - response property `order/side` deprecated
  - added the required property `order/book_side` to the response with the `200` status
  - …1 more
- **2026-04-13** `218c1f661cbd`: 10 breaking, 2 info
  - removed the required property `order/fill_count` from the response with the `200` status
  - removed the required property `order/initial_count` from the response with the `200` status
  - removed the required property `order/maker_fees` from the response with the `200` status
  - removed the required property `order/maker_fill_cost` from the response with the `200` status
  - …8 more
- **2026-01-30** `c2d717743574`: 1 info
  - added the optional property `order/subaccount_number` to the response with the `200` status

[Operation history](https://skmtc.dev/kalshi/apis/kalshi-trade-api-manual-endpoints/changes/portfolio/orders/:order_id/get.md)

---

[API](https://skmtc.dev/kalshi/apis/kalshi-trade-api-manual-endpoints.md) - [All operations](https://skmtc.dev/kalshi/apis/kalshi-trade-api-manual-endpoints/llms.txt) - [OpenAPI document](https://skmtc.dev/kalshi/apis/kalshi-trade-api-manual-endpoints/revisions/e6691cdd1915?raw)