/kalshi/series/search

POST /api/kalshi/series/search

Price: 20 credits

List prediction-market series within a category

How to use it

List the prediction-market series in a category (Politics, Sports, Crypto, Economics, Climate and Weather, and more). Each series is a contract template — returns its ticker, title, category, tags, settlement frequency, fee structure, contract documents, trading prohibitions, and the settlement sources used to resolve its markets.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• category string required — Category of prediction-market series to list (one of: "Entertainment", "Sports", "Politics", "Elections", "Economics", "Financials", "Mentions", "Climate and Weather", "Science and Technology", "Crypto", "Companies", "World", "Health", "Commodities", "Social", "Transportation", "Exotics", "Education")
• count integer required — Max number of series to return (min: 1)

Response

• @type string (default: "KalshiSeries")
• ticker string required
• category string nullable
• tags array (default: [])
• frequency string nullable
• fee_type string nullable
• fee_multiplier number nullable
• contract_url string nullable
• contract_terms_url string nullable
• additional_prohibitions array (default: [])
• settlement_sources array (default: [])
  • @type string (default: "KalshiSeriesSettlementSource")
  • name string nullable
  • url string nullable
• product_metadata object nullable
  • @type string (default: "KalshiSeriesProductMetadata")
  • scope string nullable
  • important_info object nullable
    • @type string (default: "KalshiSeriesImportantInfo")
    • id string nullable
    • markdown string nullable
    • message string nullable
• last_updated_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.