Skip to main content
On-request flight markets are not live yet. They will be released soon, and this page describes how they will work at launch.
On-request flight markets let you trade whether a flight is canceled or delayed: one flight, on the date it is scheduled to leave, and what counts as disrupted. The market doesn’t exist until someone asks for it. You create it with one request, then trade it through the RFQ system.

Flow

  1. Check what can be created with Get Flight Disruption Market Availability.
  2. Find the flight with Get Flights.
  3. Call Create Flight Disruption Market with the flight, a cover and, for a delay, the delay basis and minutes. It returns the market_ticker, creating the market if it doesn’t exist yet.
  4. Send an RFQ for that ticker with POST /communications/rfqs.
  5. Makers quote, you accept one side, and the maker confirms. This part is the same as for any other RFQ.
  6. The market closes when the flight is scheduled to leave. Kalshi reads the flight’s status three hours after its scheduled arrival, or later, and determines the market from it.
Makers skip steps 1 to 4: the RFQ arrives as rfq_created on the communications WebSocket channel with the market’s ticker, and the ticker says which flight, cover and delay it is for (see Tickers).

What you can request

A market is defined by the flight, the cover and, for the two covers that involve a delay, how the delay is measured and how long it must be. A canceled flight resolves a delayed market to No. To cover both outcomes, use either. Not every cover is offered everywhere, and the set can differ between production and demo. The availability endpoint is the source of truth: a cover missing from its covers list can’t be created, and enabled: false means creation is off entirely. It needs no authentication. Flight. A flight is one nonstop leg of scheduled passenger service, named by five fields: carrier (the operating carrier’s 2-character code), flight_number (1 to 4 digits), departure_airport and arrival_airport (3-letter codes), and scheduled_date. A flight number that flies several legs in a day is several flights, one per leg. Date. scheduled_date is the date the flight is scheduled to leave, local to the departure airport, as YYYY-MM-DD. Delay. delayed and either markets take two more fields. cancelled markets take neither.
  • delay_basis is departure or arrival: whether the delay is measured when the flight leaves the gate or when it reaches it.
  • delay_minutes is how late the flight must be. It is a multiple of delay_step_minutes, from one step up to max_delay_minutes. Both come from the availability endpoint; they are 30 and 360 by default, so 30, 60, 90 and so on up to 360.
Timing. A new market’s flight must be scheduled to leave more than min_lead_minutes from now, and no more than max_days_ahead days out. Both come from the availability endpoint. Departure country. A new market’s flight must depart from one of the availability endpoint’s departure_countries. An empty list means every country is offered.

Find a flight

Availability says what can be created:
Look up a flight number on its departure date:
An abbreviated example:
  • The lookup returns one flight per leg the number flies that day, in departure order, and an empty list when it flies none. It returns only flights a market can still be created for.
  • carrier and flight_number in the request can be a codeshare number. The flight returned is the one that operates it, and requested_carrier and requested_flight_number carry the number you asked for. Pass the returned carrier and flight_number to the create request.
  • scheduled_date is local to the departure airport, in departure_timezone. scheduled_departure and scheduled_arrival are the published times in UTC.
  • close_time is when the flight’s markets close, and settle_after is the earliest its status is read.
  • events has one entry per offered cover, with the tickers the flight has or would get. Only the cancelled entry has a market_ticker: the other covers’ market tickers depend on the delay you ask for. A ticker listed here names an event or market that may not exist yet, so create the market before sending an RFQ.
The lookup needs authentication.

Create a market

For a cancelled market, leave out delay_basis and delay_minutes. The response leaves them out too. Sign the request like any other authenticated request (see Quick Start: Authenticated Requests), and take the flight’s five fields from a lookup result. The same request returns the same market, with created: false once it exists, until it closes. You can call it before each RFQ. An existing market is returned even when new markets are no longer offered. A market created a moment ago may not be readable yet: if GET /markets/{ticker} returns 404 right after creation, retry. Then request quotes on it with POST /communications/rfqs:
Sizing, quoting, acceptance and timing follow Request for Quote (RFQ). These markets use the shorter High Volatility Market windows: a maker has 3 seconds to confirm an accepted quote, and execution can start 1 second after that. Execution can still fail (for example, a post-only maker order that would cross), so take the outcome from the execution event or your fills, not from the timing.

Tickers

A ticker fully defines its market, so a maker can tell what an RFQ is for from the ticker alone. KXRFQFLIGHTD-AA100-JFKLHR-26NOV25-DEP120 The first four segments are the event ticker. An event holds every market of its cover for the flight, so KXRFQFLIGHTD-AA100-JFKLHR-26NOV25 can hold DEP60, DEP120 and ARR90 side by side. A flight with all three covers has three events, one in each series.

Finding these markets

Series starting with KXRFQ are left out of unscoped listings, so that markets created for one request don’t crowd out everything else:
  • GET /markets and GET /historical/markets skip them unless the request sets series_ticker, event_ticker or tickers to one of them. On GET /markets, mve_filter=exclude skips them even then. GET /historical/markets takes only one of those four filters at a time.
  • GET /markets/trades and GET /historical/trades skip their trades unless the request sets ticker.
  • GET /events leaves them out, including when the request sets series_ticker to one of their series. GET /series leaves their series out.
  • The WebSocket trade and ticker channels deliver them only to subscriptions that list the market. market_lifecycle_v2 leaves them out.
Fetching one by ticker works as for any market: GET /markets/{ticker}, GET /events/{event_ticker} and GET /series/{series_ticker}.

Settlement

  • The market closes when the flight is scheduled to leave (close_time).
  • Kalshi determines it from the flight’s status as Cirium reports it, read on or after the scheduled arrival plus three hours. latest_expiration_time is five days after that earliest read time.
  • A delay is the actual gate time minus the published time, as Cirium reports them, in whole minutes rounded down. Where Cirium reports no published time, the scheduled gate time is used. departure compares the gate departures and arrival the gate arrivals.
  • A delay equal to delay_minutes counts: a flight exactly 120 minutes late resolves a 120-minute market to Yes.
  • If a reading can’t decide the market yet (the flight is still in the air, or its gate times aren’t reported), the market waits and the flight is read again later, so a later landing can still settle it automatically. If Cirium reports the flight as diverted, or the market still can’t be decided by its latest_expiration_time, the exchange determines it.
Each market’s rules_primary and rules_secondary carry the full terms.

Limits and errors

The create endpoint is charged against your write rate limit, and the lookup against your read limit. Creation and lookup limits are separate from request-rate limits. The specific reason is in the error’s details when there is one; a rate-limit error can come without it. A missing or malformed query parameter on the lookup returns 400 before the request is looked at further. Such a 400 comes before authentication, with a body of the form {"msg": "<reason>"} and no error object.