During development, you can use the developer endpoints
without an API key. For production use, you’ll need an
API key to avoid rate limits.
Get Events with Nested Markets
You get events (real-world questions) and include their nested markets so you can read outcome mints from theaccounts field. If you need the data
model, review Event fields.
Get Events with Nested Markets
Get Events with Nested Markets
Filter Events by Market Status
Filter events to focus on markets that match a given status (for example, active vs. initialized). If you need the full status flow, see Prediction Market Lifecycle.Get Active Markets
Get Active Markets
Get Initialized Markets
Get Initialized Markets
Get All Markets for a Specific Asset
If you know the asset you want (e.g., Bitcoin, SOL), the fastest approach is to query the events endpoint directly with theseriesTickers parameter. Each
asset has a root series ticker (e.g., KXBTC for Bitcoin, KXSOL for SOL)
that covers all market types for that asset.
Get All Active Bitcoin Markets
Get All Active Bitcoin Markets
/api/v1/series?category=Crypto&tags=SOL returns all series tickers that
start with KXSOL. You can then pass those tickers to the events endpoint.
For broader discovery without a specific asset in mind, use the categories
and tags approach below.
Filter Events by Categories and Tags
Use tags to find relevant series (event templates) and then get events for those series. This keeps discovery focused without hardcoding tickers.Get Tags by Category
Get Tags by Category
Filter Series by Category and Tags
Filter Series by Category and Tags
Get Events by Series Tickers
Get Events by Series Tickers
Review API Responses
Use event and series responses to extract outcome mints and filter markets. If you only need outcome mints, you can skip to theaccounts map in each
market object.
Events Response
You receive event metadata and nested markets (whenwithNestedMarkets=true),
including yesMint and noMint in market accounts.
Tags by Categories Response
You receive a map of categories to tag arrays, which you use to filter series.Series Response
You receive series metadata, including ticker, title, category, tags, and frequency.KYC Requirements
Prediction market applications must use Proof to meet Kalshi compliance requirements.API Routes
Cookbook Repository
This recipe, along with many more, is available in the DFlow Cookbook Repo. You can clone it and start coding immediately.Need Help?
Email Support
Reach out to our team at [email protected] for technical support,
partnership inquiries, or general questions.
Join Our Discord
Connect with other developers, get help, and stay updated on the latest
DFlow developments.
Dev Notifications
Join the DFlow Dev Notifications Telegram group to stay in the loop on
new features and other announcements.