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

# Kalshi Get Orders

Get open and historical orders from your Kalshi portfolio. Returns order details including status, price, side, type, and fill counts. Supports filtering by ticker, event, status, and time range. Ideal for: order management, trade monitoring, execution analysis, automated order tracking workflows.

![Kalshi Get Orders logo](https://cdn.b3.fun/kalshi-logo.png)
Catalog action Utility kalshi

Get open and historical orders from your Kalshi portfolio. Returns order details including status, price, side, type, and fill counts. Supports filtering by ticker, event, status, and time range. Ideal for: order management, trade monitoring, execution analysis, automated order tracking workflows.


## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `kalshi-get-orders` |
| Category | Utility |
| Connector | `kalshi` |
| Requires gas | No |
| Funds movement | None declared |
| Tags | `kalshi`, `prediction-market`, `orders`, `trading`, `read` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `ticker` | `string` | No | Filter by market ticker |
| `eventTicker` | `string` | No | Filter by event ticker |
| `status` | `string` | No | Filter by order status |
| `limit` | `number` | No | Maximum number of orders to return \(default: 100, max: 1000\) |
| `cursor` | `string` | No | Cursor for pagination |
| `minTs` | `number` | No | Minimum timestamp \(Unix seconds\) to filter orders |
| `maxTs` | `number` | No | Maximum timestamp \(Unix seconds\) to filter orders |
| `subaccount` | `number` | No | Subaccount number \(0 = primary, 1-32 = subaccounts\) |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `orders` | `array` | Yes | List of orders |
| `cursor` | `string` | Yes | Cursor for fetching the next page |

## Examples

**Workflow node**

```json
{
  "type": "kalshi-get-orders",
  "payload": {
    "ticker": "example-ticker",
    "eventTicker": "example-eventTicker",
    "status": "resting",
    "limit": 100,
    "cursor": "example-cursor"
  },
  "children": [],
  "connector": {
    "type": "kalshi",
    "id": "conn_kalshi"
  }
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/kalshi-get-orders/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "ticker": "example-ticker",
    "eventTicker": "example-eventTicker",
    "status": "resting",
    "limit": 100,
    "cursor": "example-cursor"
  }
}'
```

**Use expressions for dynamic values**

Payload fields can use workflow expressions such as `{{$trigger.body.amount}}`, `{{$nodes.fetch.result.price}}`, and `{{$props.asset}}` when the value should come from a trigger, prior node, or reusable workflow prop.