NewsCryptoKalshi Rolls Out On-Demand Event Contracts, Starting With Custom Weather and Concert RFQs

Kalshi Rolls Out On-Demand Event Contracts, Starting With Custom Weather and Concert RFQs

Author: CryptoNewsNet·

Key Takeaways

  • •Kalshi's new API framework enables traders to create event contracts on demand from pre-set templates instead of waiting for the exchange to list them.
  • •Markets generated through the feature, known as "on-request" markets, do not exist until a user requests their terms, and their first price comes from an RFQ process in which market makers have three seconds to confirm quotes.
  • •The feature is currently restricted to API users, with live weather contracts covering measurable-rain thresholds in the contiguous US and concert cancellation or postponement templates slated to launch soon.
  • •Kalshi's Head of Institutional, Andy Ross, said listing requested markets on day one carries value because early prices can inform positions in conventional markets before an event contract has enough liquidity to trade at scale.
  • •Because the exchange returns the existing ticker when an identical market is requested again, a hedge created by one trader becomes reusable by others with the same exposure.
Kalshi Rolls Out On-Demand Event Contracts, Starting With Custom Weather and Concert RFQs

Kalshi Rolls Out On-Demand Event Contracts, Starting With Custom Weather and Concert RFQs

Kalshi is moving to automate custom risk hedging on its platform, rolling out an API framework that allows traders to generate on-demand event contracts rather than waiting for the exchange to list them. The system is already live for certain types of weather contracts and is set to expand to concert schedules.

Users create contracts from pre-set templates by specifying coordinates, dates, or events. Once a contract ticker is generated, traders can tap market makers for liquidity through a private request-for-quote (RFQ) process before the trade reaches the public order book.

Kalshi calls these "on-request" markets because a contract does not exist until someone requests its terms. At this stage, the feature is available only to API users, so taking part currently requires programmatic integration.

How a New Market Gets a Price

To create a market and obtain a price, a user submits parameters within a template defined by Kalshi. The exchange creates the market and returns its ticker, or returns the existing ticker if the same market has already been created.

The user then sends this ticker along with a request for quote (RFQ) for the amount they want to trade, and Kalshi broadcasts the request to available market makers. For a contract generated on demand, this quoting step is what produces the market's first price, since it starts with no trading history of its own.

If the user accepts a quote and a maker confirms it, the exchange enters the orders into its public book. A fill is still not guaranteed. Kalshi's RFQ documentation gives makers three seconds to confirm quotes for these markets.

Kalshi keeps these individually created contracts out of its general API listings so they do not crowd out other markets. Users can still locate them by ticker or by filtering the API for the on-request weather series. And because the exchange returns the existing ticker whenever an identical market has already been created, a hedge requested by one trader becomes reusable by the next person with the same exposure.

The Feature Builds on Institutional Precedent

In an October interview with Finance Magnates, Kalshi's Head of Institutional, Andy Ross, described how the exchange has listed markets at the request of individual firms.

"Day one, there's value in listing a market and having it priced," Ross said.

A price on a specific political or legislative outcome, for example, can inform decisions about positions in conventional markets before the event contract itself has enough liquidity to trade the exposure at scale.

Earlier this year, Kalshi enabled request-for-quote (RFQ) workflows for market makers and hedge funds using the Talos trading environment. The integration allows institutional traders to automate execution strategies and negotiate larger transactions without establishing a separate connection to the exchange.

The new API could in effect reduce the case-by-case listing that would otherwise be required where an exposure fits an existing template. Kalshi sets the qualifying criteria and settlement terms in advance, so a user can simply specify an exposure and a maker can see exactly what the contract is from its ticker, according to Kalshi's contract documentation.

What Kalshi Supports Today

In production, the weather service lets users enter coordinates, a time window, and a threshold for the number of hours with measurable rain. Kalshi limits live weather contracts to the contiguous US. The other weather variables described in Kalshi's weather market guide are available in the company's demo environment.

Kalshi says its concert markets will launch soon. Per the exchange's concert market guide, the templates would cover cancellation or postponement of a specific show that meets the exchange's venue and scheduling criteria.

How broadly on-demand listing can ultimately be used will depend on which templates Kalshi activates and which clients it allows to request them. In the near term, the observable markers are whether the demo-only weather variables move into production, when the promised concert templates actually go live, and whether request access widens beyond API users.