POST /api/kalshi/markets
Price: 1 credit
Get a tradeable Yes/No prediction-market contract by its ticker
Get full details of a single prediction-market contract by its ticker. Returns the current Yes/No bid and ask prices, last and previous trade price, traded volume (total and 24h), open interest, liquidity, contract status, title and subtitles, the primary and secondary settlement rules, the settled result (when closed), and open/close/expiration timestamps.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)ticker string required — Market ticker of the tradeable Yes/No contract (examples: "KXELONMARS-99", "KXNBAGAME-26JAN16LALBOS-BOS"; minLength: 1)@type string (default: "KalshiMarket")ticker string requiredevent_ticker string nullablemarket_type string nullablestatus string nullablesubtitle string nullableyes_sub_title string nullableno_sub_title string nullableyes_bid number nullableyes_ask number nullableno_bid number nullableno_ask number nullablelast_price number nullableprevious_price number nullableprevious_yes_bid number nullableprevious_yes_ask number nullableyes_bid_size integer nullableyes_ask_size integer nullablevolume integer nullablevolume_24h integer nullableopen_interest integer nullableliquidity number nullablenotional_value number nullablefloor_strike number nullablestrike_type string nullablerules_primary string nullablerules_secondary string nullableresult string nullableexpiration_value string nullablesettlement_value number nullablecan_close_early boolean nullableearly_close_condition string nullablesettlement_timer_seconds integer nullableopen_at string nullableclose_at string nullableexpiration_at string nullableexpected_expiration_at string nullablelatest_expiration_at string nullablecreated_at string nullableupdated_at string nullablesettled_at string nullable422 — 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 — Market not found 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.