dc185044-1
Kalshi Opens Custom Rain Contracts Through an API
Kalshi's API-only workflow creates custom measurable-rain contracts across the contiguous U.S., then routes RFQs to market makers with a three-second confirmation window.

Outputs
Kalshi's on-demand weather workflow is currently available only to API users.
The live weather service covers the contiguous United States.
Contracts use three inputs: location, measurement period and hours-of-measurable-rain threshold.
Market makers have three seconds to confirm quotes, and a completed trade is not guaranteed.
Concert templates remain awaiting launch and cover eligible show cancellations or postponements.
Kalshi has opened API-only creation of customized measurable-rain contracts across the contiguous United States, with market makers given three seconds to confirm quotes.
The exchange’s process lets users define a weather exposure before any trade reaches its public order book. Users specify three elements: a location, a measurement period, and a threshold for hours of measurable rain. Kalshi’s live weather service covers the contiguous United States.
That order of operations separates contract formation from order placement. Once a user submits those parameters, Kalshi creates the contract and returns its ticker. If the same contract already exists, the exchange returns the existing ticker instead, allowing users to reuse the identifier rather than create a duplicate instrument.
What does this change for API users?
The practical change is that API users can specify contract terms before seeking pricing. They then submit what Kalshi describes as a "request for quote" (RFQ) for their desired trade size. Kalshi sends that request to available market makers.
If a user accepts a quote and a market maker confirms it, Kalshi enters the associated orders into its public order book. This creates a staged market structure: on-demand contract creation and direct quote solicitation come first, followed by public order-book posting after mutual confirmation.
The three-second quote-confirmation window adds a timing condition to that process. A completed trade is not guaranteed. RFQ acceptance alone therefore does not establish execution; the market maker must also confirm within its allotted time.
Contracts created this way do not appear in Kalshi’s general API listings. Users can retrieve them by ticker or filter for the "on-request weather series." That makes the returned ticker a key integration field for clients that need to locate and monitor contracts created through the new process.
The workflow also distinguishes the act of defining a contract from the act of trading it. Creating a ticker establishes the specified measurable-rain exposure, while retrieving an existing ticker identifies a contract already created with matching terms. The RFQ then seeks a quote for the requested trade size, and the exchange publishes the accepted orders only after confirmation.
For API users, the operational test is whether their systems can retain the ticker, submit the intended trade size and accommodate the three-second confirmation deadline. On-demand creation removes the need to wait for a matching contract to appear in general listings, but it does not remove execution risk: quote acceptance and market-maker confirmation remain separate conditions.
Concert templates are the next distinct product extension. Kalshi’s concert contracts remain awaiting launch. They are designed for contracts tied to the cancellation or postponement of specific shows that satisfy the exchange’s venue and scheduling criteria.
That design places eligibility before event outcome. A show must meet Kalshi’s venue and scheduling standards, and the resulting contract would concern whether the performance is canceled or postponed. Those templates are not yet part of the live on-demand workflow.
The rain workflow uses measurable weather inputs; concert contracts use event-status outcomes. Kalshi is keeping the two forms of exposure on separate launch tracks: a live API process for measurable rain and pending templates for eligible concerts.
For market participants, that distinction determines the reference event each contract tracks: measurable rain for the current product, or the status of an eligible show for the pending templates. The next structural change will be the concert-template launch; until then, API creation remains confined to the live measurable-rain workflow.
via tokenpost.com (Source)
More from Nathan Brooks
Show full bio
Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,651 articles