Create a Kalshi mirror market#

On the web Reclaim submission page or mobile external-market screen, use the Kalshi market link or ticker field. Paste a Kalshi event URL to select a binary market, or paste a URL with marketTicker to select that exact market. Choose Create on Seesaw, generate the Reclaim proof with your configured runner, then review the proof and approve the wallet transactions.

Creation completes after allocation and Open confirm. If it stops after Begin, retry with the same proof and wallet to resume. This mirrors the market's outcome; it does not copy Kalshi's orders or liquidity.

The runner export/import and pairing flow is shared with Polymarket. Credentials stay with the runner. The default Polymarket flow is still available beside Kalshi.

CLI and API#

bash

seesaw reclaim kalshi markets --query 'https://kalshi.com/markets/SERIES/SLUG/EVENT'
seesaw reclaim kalshi prepare --query MARKET_TICKER --operation create
seesaw reclaim kalshi prepare --query MARKET_TICKER --operation resolve

For an event with multiple markets, use markets first and pass one returned ticker to prepare. Save data.request and generate its proof with the runner, then submit with seesaw reclaim submit.

The public lookup endpoint is GET /api/v1/external-markets/discover?provider=kalshi&q=MARKET_LINK_OR_TICKER. Kalshi pagination uses cursor/nextCursor. Omit the query to browse; closed=true lists finalized markets. Unsupported combinations and non-binary markets are excluded. Large events require a specific market link.

Template and deployment#

New Kalshi requests use template V4, matching REST active and ISO close_time for creation. Resolution requires finalized and exact result/payout pairs: yes/1.0000, no/0.0000, or scalar/0.5000 (VOID refund). The captured facts must belong to the same market object. Determined, disputed, and merely closed markets cannot resolve through this flow. V3 commitments remain frozen and existing V3 policies remain supported onchain.