/kalshi/events/search

POST /api/kalshi/events/search

Price: 20 credits

Search prediction-market events by series and lifecycle status

How to use it

List prediction-market events with filters — narrow to a single series or restrict by lifecycle status (unopened, open, closed, settled). An event is the question that groups one or more tradeable Yes/No contracts. Each result carries the event title and subtitle, category, whether the outcomes are mutually exclusive, and — when with_nested_markets is set — every tradeable contract of the event with its live prices, volume, open interest and settlement rules.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of events to return (min: 1)
• status string nullable — Filter events by lifecycle status (one of: "unopened", "open", "closed", "settled", "active")
• series_ticker string nullable — Return only events that belong to this series
• with_nested_markets boolean — Include all tradeable contracts of each event in the response (default: false)

Response

• @type string (default: "KalshiEvent")
• event_ticker string required
• series_ticker string nullable
• subtitle string nullable
• category string nullable
• mutually_exclusive boolean nullable
• collateral_return_type string nullable
• strike_period string nullable
• last_updated_at string nullable
• markets array nullable
  • @type string (default: "KalshiMarket")
  • ticker string required
  • event_ticker string nullable
  • market_type string nullable
  • status string nullable
  • subtitle string nullable
  • yes_sub_title string nullable
  • no_sub_title string nullable
  • yes_bid number nullable
  • yes_ask number nullable
  • no_bid number nullable
  • no_ask number nullable
  • last_price number nullable
  • previous_price number nullable
  • previous_yes_bid number nullable
  • previous_yes_ask number nullable
  • yes_bid_size integer nullable
  • yes_ask_size integer nullable
  • volume integer nullable
  • volume_24h integer nullable
  • open_interest integer nullable
  • liquidity number nullable
  • notional_value number nullable
  • floor_strike number nullable
  • strike_type string nullable
  • rules_primary string nullable
  • rules_secondary string nullable
  • result string nullable
  • expiration_value string nullable
  • settlement_value number nullable
  • can_close_early boolean nullable
  • early_close_condition string nullable
  • settlement_timer_seconds integer nullable
  • open_at string nullable
  • close_at string nullable
  • expiration_at string nullable
  • expected_expiration_at string nullable
  • latest_expiration_at string nullable
  • created_at string nullable
  • updated_at string nullable
  • settled_at string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.