Events when markets are created or resolved and when match groups are created or updated. Optionally subscribe to everything with a wildcard subscription.
Overview
Use case: Keep catalogs and UIs in sync with new markets and settlements.
Requirements
- Pro or Enterprise API key.
- Subscribe with market_ids and/or group_ids, or omit both to receive all lifecycle events (wildcard).
- Wildcard still counts toward your tier subscription limits.
Send
| Field | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | Must be "subscribe" for this section. |
| channel | string | yes | Must be "market_lifecycle". |
| market_ids | string[] | optional | Market scope; can be combined with group_ids. |
| group_ids | number[] | optional | Group scope; expands to markets linked to each group. |
| wildcard | behavior | optional | Omit both market_ids and group_ids to receive all channel events. |
Receive
Data messages use the standard envelope: channel, type, ts, data. Types for this channel include: market_created, market_resolved, group_created, group_updated.
Data fields (inside data)
| Field | Type | Description |
|---|---|---|
| type | string | market_created, market_resolved, group_created, group_updated, etc. |
| market_id | string? | When applicable. |
| source | string? | Venue. |
| group_id | number? | Match group when applicable. |
| title | string? | Human-readable title when provided. |
| resolution | string? | On resolution events when provided. |





