> ## 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 Market

Get detailed information about a Kalshi prediction market by ticker. Returns pricing, volume, open interest, status, and settlement data. Ideal for: market monitoring, price tracking, portfolio analysis, automated trading signals.

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

Get detailed information about a Kalshi prediction market by ticker. Returns pricing, volume, open interest, status, and settlement data. Ideal for: market monitoring, price tracking, portfolio analysis, automated trading signals.


## At a Glance

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

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `ticker` | `string` | Yes | The market ticker \(e.g., 'KXBTC-25MAR14-B95500'\) |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `ticker` | `string` | No | Market ticker |
| `title` | `string` | No | Market title \(e.g. 'Will Bitcoin close above $95,500 on March 14?'\) |
| `event_ticker` | `string` | No | Parent event ticker |
| `market_type` | `string` | No | Market type \(binary or scalar\) |
| `subtitle` | `string` | No | Market subtitle |
| `yes_sub_title` | `string` | No | Yes side subtitle |
| `no_sub_title` | `string` | No | No side subtitle |
| `status` | `string` | No | Market status \(unopened, open, closed, settled\) |
| `yes_bid_dollars` | `string` | No | Current best bid for Yes contracts \(dollar string, e.g. '0.5600'\) |
| `yes_ask_dollars` | `string` | No | Current best ask for Yes contracts \(dollar string\) |
| `no_bid_dollars` | `string` | No | Current best bid for No contracts \(dollar string\) |
| `no_ask_dollars` | `string` | No | Current best ask for No contracts \(dollar string\) |
| `last_price_dollars` | `string` | No | Last trade price \(dollar string\) |
| `previous_price_dollars` | `string` | No | Previous session price \(dollar string\) |
| `previous_yes_bid_dollars` | `string` | No | Previous session Yes bid \(dollar string\) |
| `previous_yes_ask_dollars` | `string` | No | Previous session Yes ask \(dollar string\) |
| `volume_fp` | `string` | No | Total contracts traded \(fixed-point string, e.g. '10.00'\) |
| `volume_24h_fp` | `string` | No | Contracts traded in last 24 hours \(fixed-point string\) |
| `open_interest_fp` | `string` | No | Open interest in contracts \(fixed-point string\) |
| `open_time` | `string` | No | Market open time \(ISO 8601\) |
| `close_time` | `string` | No | Market close time \(ISO 8601\) |
| `expiration_time` | `string` | No | Market expiration time \(ISO 8601\) |
| `result` | `string` | No | Market result \(empty if unsettled\) |
| `settlement_value_dollars` | `string \| null` | No | Settlement value in dollars \(null if unsettled\) |
| `rules_primary` | `string` | No | Primary market rules |
| `can_close_early` | `boolean` | No | Whether the market can close early |
| `notional_value_dollars` | `string` | No | Notional value of the contract \(dollar string\) |
| `cap_strike` | `number \| null` | No | Cap strike price |
| `floor_strike` | `number \| null` | No | Floor strike price |

## Examples

**Workflow node**

```json
{
  "type": "kalshi-get-market",
  "payload": {
    "ticker": "example-ticker"
  },
  "children": []
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/kalshi-get-market/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "ticker": "example-ticker"
  }
}'
```

**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.