Events (questions) grouping markets
API · /kalshi-api
Kalshi Event Markets API
Live market data from Kalshi, the CFTC-regulated US event-contract exchange, served from its public trade API. Kalshi lists yes/no contracts that settle on real-world outcomes — elections, economics, Federal Reserve decisions, weather, sports and world events — and the executed price is the market-implied probability of that outcome. The trades endpoint returns the recent public trade tape: the executed price (as cents and as a 0-1 probability), the size, the taker side and the time — the live pulse of what is actually trading. The events endpoint lists the events (the questions) that group markets, with their category and series. The markets endpoint is the contract directory — every tradable market with its ticker, the yes outcome it settles on, its status and open/close times — filterable by event, series or status. This is a regulated real-money event-contract venue — live implied probabilities and order flow — distinct from the play-money (Manifold), political (PredictIt) and crypto (Polymarket) prediction-market APIs in the catalogue. Live order-book snapshots are gated behind authentication upstream, so prices are sourced from the public trade tape. Live, no key on the upstream, nothing stored.
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 221 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 3,640
- attiva
- Chiamate totali
- 0
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 21,000 chiamate/mese
- 5 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 21.000 Aufrufe/Monat
- 5 req/sec
- Trade tape, events & directory
- Keine Kreditkarte
Starter
€8.15 /mese
- 245,000 chiamate/mese
- 15 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 245k Aufrufe/Monat
- 15 req/sec
- Vollständige Ereignisabdeckung
- E-Mail-Support
Pro
€24.40 /mese
- 1,050,000 chiamate/mese
- 40 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 1,05 Mio. Aufrufe/Monat
- 40 req/sec
- Prognose- und Signal-Pipelines
- Priority-Support
Scale
€55.60 /mese
- 3,700,000 chiamate/mese
- 100 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 3,7 Mio. Aufrufe/Monat
- 100 req/sec
- Schreibtisch-/Forschungsumfang
- Dedizierte SLA
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Crypto Order Flow & CVD API
Who is actually hitting the market — buyers or sellers — read live from Binance's aggregated trade tape, no key, nothing stored. Every trade carries a flag for which side was the aggressor: a taker buy lifts the ask, a taker sell hits the bid. Summing those over a window gives order flow — the net buying or selling pressure that price action follows — and its running total is the Cumulative Volume Delta (CVD), the metric order-flow traders watch to spot absorption and divergence. The flow endpoint scans the recent aggregated trades for a pair (up to 5,000) and returns the taker-buy and taker-sell volume in base and quote, the delta (buy minus sell), the CVD over the window, the buy/sell ratio, the share of volume that was buying, a net-pressure label and the time span covered. The large endpoint surfaces the big prints — single aggressive trades above a notional threshold — and tags each as a taker buy or sell, so you see the whale orders moving the tape, with the buy- and sell-side large-trade totals. The symbols endpoint lists tradable pairs. This is the trade-flow / CVD microstructure analytics cut for crypto — distinct from the raw recent-trades feed, the order-book depth and the price, ticker and slippage APIs in the catalogue. Pairs are Binance symbols (BTCUSDT) or a coin=BTC"e=USDT form.
api.oanor.com/orderflow-api
Crypto Options Max Pain & Open Interest API
Where the crypto options market is positioned, and the strike toward which an expiry's open interest exerts the most "pain" — computed live from Deribit's public option book, no key, nothing stored. Max pain is the strike at which the total value of all open options is lowest at expiry: the price at which the greatest dollar amount of option open interest expires worthless and option writers keep the most premium. Traders watch it because price often gravitates toward max pain into a large expiry. The maxpain endpoint takes a currency (BTC, ETH, SOL, XRP) and an expiry and returns the max-pain strike, the spot/underlying, how far spot sits from max pain, and the call and put open-interest totals with the put/call OI ratio. The oi endpoint returns the full open-interest-by-strike distribution for an expiry — which strikes hold the most open interest, the magnets and walls (support & resistance) traders watch. The expiries endpoint lists every listed expiry with its aggregate open interest, contract count and call/put split. This is the aggregate options-positioning / max-pain analytics cut for crypto — distinct from the raw per-contract option chain (greeks/IV), from US equity options and from the crypto-volatility APIs in the catalogue. Currency is BTC, ETH, SOL or XRP; expiry is a Deribit code like 26JUN26.
api.oanor.com/maxpain-api
Crypto Slippage & Market Impact API
What a crypto trade actually costs once it eats into the order book — computed live from Binance's full depth feed (up to 5000 levels per side), no key, nothing stored. Top-of-book price is a fiction for anything but the smallest order: a real market order walks down the book, filling progressively worse levels, and the gap between the quoted price and the realised average fill is slippage. The estimate endpoint takes a pair, a side (buy or sell) and a size — in quote currency (notional, e.g. $250,000) or in base coin (quantity) — walks the live book level by level and returns the average fill price, the slippage versus the mid and versus top-of-book, the price impact (how far the last filled level sits from mid), the number of levels consumed and whether the book even holds enough liquidity to fill. The depth endpoint returns a liquidity profile: top bid/ask, mid, spread and the cumulative bid- and ask-side liquidity sitting within ±0.1%, ±0.25%, ±0.5%, ±1% and ±2% of mid, plus the book imbalance — a one-glance read on how deep and how lopsided a market is. The symbols endpoint lists tradable pairs. This is the execution-cost / market-impact analytics cut for crypto — distinct from the raw exchange order-book feed, from VWAP-on-candles, and from the price, ticker and quote APIs in the catalogue. Pairs are Binance symbols (BTCUSDT) or a coin=BTC"e=USDT form.
api.oanor.com/slippage-api
Trending Stocks API
Die Ticker, nach denen die Leute gerade suchen, bereitgestellt aus dem öffentlichen Trending-Feed von Yahoo Finance. Dies ist ein Aufmerksamkeits- und Einzelhandelsinteresse-Signal, keine Preisbewegungsliste: Der Trending-Endpoint gibt die meistgesuchten Symbole in einer Region zurück (USA, Großbritannien, Deutschland, Frankreich, Indien, Brasilien und mehr) und reichert jedes mit seinem Live-Preis, der Tagesänderung und der Börse an – so sehen Sie, was Aufmerksamkeit erregt und wie es sich bewegt. Der Ticker-Endpoint beantwortet die Frage „Ist dieses Symbol gerade im Trend und wo rangiert es?“. Der Regions-Endpoint listet die unterstützten Märkte auf. Dies ist der Suchaufmerksamkeits-/Sentiment-Datenschnitt für Aktien – was der Einzelhandel beobachtet – unterschieden von den preisbasierten Marktbewegern, den Live-Quote- und Intraday-Candle-APIs im Katalog. Trending spiegelt das Suchinteresse und Verschiebungen während des Handelstages wider. Live, kein Key vorgeschaltet, nichts gespeichert.
api.oanor.com/trendingstocks-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Kalshi Event Markets API?
Qual è il limite di velocità di Kalshi Event Markets API?
Quanto costa Kalshi Event Markets API?
Posso cancellare l'abbonamento in qualsiasi momento?
Kalshi Event Markets API è conforme al GDPR?
Scegli un endpoint dall'elenco a sinistra per visualizzarne i dettagli e provarlo.
Frammenti di codice
Iscriviti per ottenere una chiave API, quindi chiama qualsiasi percorso sotto il tuo slug.
curl https://api.oanor.com/kalshi-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/kalshi-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/kalshi-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/kalshi-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Valutazioni
Accedi per votare.
Nessuna recensione ancora.
Discussione
Fai domande, condividi consigli, ricevi risposte dal provider e dagli altri sviluppatori. Pubblico — chiunque può leggere.
Accedi per scrivere o rispondere.
AccediNuova discussione
·
-
Risposta del provider
🔒 Discussione bloccata — non si può più rispondere.
-
·
- Nessuna discussione — inizia tu.
Supporto
Supporto privato 1:1 con il provider — fatturazione, integrazione, account. Solo tu e il team del provider vedete questi thread.
Accedi per aprire un ticket di supporto.
AccediApri nuovo ticket
Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.
-
·
Urgente - Nessun ticket per questa API.