Skip to main content
POST
Create Concert Cancellation Market

Authorizations

KALSHI-ACCESS-KEY
string
header
required

Your API key ID

KALSHI-ACCESS-SIGNATURE
string
header
required

Base64 signature of the pre-sign text (timestamp + method + path) made with the API key's algorithm - RSA-PSS with SHA-256 for RSA keys, Ed25519 for Ed25519 keys

KALSHI-ACCESS-TIMESTAMP
string
header
required

Request timestamp in milliseconds

Body

application/json
jambase_event_id
string
required

The show, as jambase:<id>, from the concert listing or search.

Example:

"jambase:16543035"

scheduled_date
string
required

The venue-local date the show is scheduled for, as YYYY-MM-DD. It must match the show's current listing.

Example:

"2026-11-20"

cover
enum<string>
required

What a concert cancellation market pays on, read from the show's listing after its scheduled date has ended:

  • postponed: Yes when the show is listed as postponed, or as taking place on any other date. A show listed as canceled resolves to No.
  • cancelled: Yes when the show is listed as canceled.
  • either: Yes in both of those cases.
Available options:
postponed,
cancelled,
either

Response

Market returned or created successfully

cover
enum<string>
required

What a concert cancellation market pays on, read from the show's listing after its scheduled date has ended:

  • postponed: Yes when the show is listed as postponed, or as taking place on any other date. A show listed as canceled resolves to No.
  • cancelled: Yes when the show is listed as canceled.
  • either: Yes in both of those cases.
Available options:
postponed,
cancelled,
either
event_ticker
string
required

Event ticker of the market.

Example:

"KXRFQCONCERTP-JB16543035-26NOV20"

market_ticker
string
required

Market ticker of the market.

Example:

"KXRFQCONCERTP-JB16543035-26NOV20-PPD"

created
boolean
required

False when a market for the same request already existed.