> Full docs in one file: https://kacdata.com/llms-full.txt

# Lifecycle

Source: https://kacdata.com/docs/schemas/lifecycle

> Schema for Kalshi market and event lifecycle messages.

Each row is a message from the Kalshi `market_lifecycle_v2` channel. One file per UTC day holds every market and event.

**Data type:** `lifecycle` ·

## Schema

| Field | Type | Description |
| --- | --- | --- |
| `market_ticker` | `string \| null` | Kalshi market ticker. Null for event-level messages. |
| `event_ticker` | `string \| null` | The event the message belongs to: set on event-level messages and on `created` market messages. |
| `timestamp` | `timestamp[us] \| null` | Source time: `determination_ts` for `determined`, `settled_ts` for `settled`. Null for other messages. |
| `local_timestamp` | `timestamp[us]` | KacData receive timestamp. |
| `event_type` | `string` | Message type: `market_lifecycle_v2`, `event_lifecycle` or `event_fee_update`. |
| `market_lifecycle_json` | `string` | The message body as received, unmodified JSON. |

## Message types

- `market_lifecycle_v2` — market-level messages. The JSON field `event_type` says what happened: `created`, `activated`, `deactivated`, `close_date_updated`, `determined`, `settled`, `price_level_structure_updated`, `metadata_updated`, and others. The result is in `result` and the settlement value in `settlement_value` (a dollar string; values other than 0 and 1, such as `"0.5000"`, occur).
- `event_lifecycle` — event-level messages with the event's `title`, `subtitle`, `series_ticker` and `collateral_return_type`.
- `event_fee_update` — event fee changes, with `fee_type_override` and `fee_multiplier_override`.

## Download URL

```text
https://api.kacdata.com/v1/kalshi/lifecycle/{YYYY}/{MM}/{DD}/markets_lifecycle.parquet
```
