List Markets
curl --request GET \
--url https://api.simmer.markets/api/sdk/markets{
"detail": [
{
"loc": [
"<string>"
],
"msg": "<string>",
"type": "<string>",
"input": "<unknown>",
"ctx": {}
}
]
}Markets
List Markets
List markets available for SDK trading.
By default, excludes tracking markets (no AI counterparty for simmer trading). Set include_analytics_only=true to include them (for real trading only).
Parameters:
- status: Filter by status (‘active’, ‘resolved’, etc.). Omit to get all statuses when using ids.
- venue: Filter by venue (‘polymarket’, ‘sim’). Alias for import_source. Deprecated: ‘sandbox’/‘simmer’ are accepted but deprecated, use ‘sim’ instead.
- import_source: Same as venue (kept for backwards compatibility).
- q: Text search for market questions (min 2 chars, case-insensitive)
- ids: Comma-separated market IDs to fetch (max 50). When provided, status filter is optional.
- tags: Comma-separated tags to filter by (e.g., ‘weather’ or ‘weather,crypto’). Returns markets with ALL specified tags.
- sort: ‘volume’ (by 24h volume), ‘created’ (by created_at), or None (default by created_at)
- include: Comma-separated optional response fields.
resolution_criteriais returned by default for active-market source verification; the include value remains accepted for older SDK callers. - tradeable_only: Defaults true. Set false to include active DB rows even when Redis/CLOB liveness checks mark the orderbook unavailable.
Each market row includes seconds_to_resolution (float seconds until
resolves_at, server-computed at response time; null when the market has
no resolution timestamp, negative once it has passed). Prefer it over
computing expiry from resolves_at locally — it is immune to host clock
skew and matches replay semantics.
Unknown params will trigger a warning in the response (helps debug typos). Requires API key in Authorization header.
GET
/
api
/
sdk
/
markets
List Markets
curl --request GET \
--url https://api.simmer.markets/api/sdk/markets{
"detail": [
{
"loc": [
"<string>"
],
"msg": "<string>",
"type": "<string>",
"input": "<unknown>",
"ctx": {}
}
]
}Need
time_to_resolution, slippage, or flip-flop detection? Use the context endpoint — those fields are not on /markets."truncated": true and a total field showing how many matched. Use tags, q, or venue filters to narrow large result sets.
Response fields
Each entry inmarkets[] has the same shape as GET /api/sdk/markets/{market_id}. See that page for the full field reference, including resolution fields (status, resolved_at, outcome).Query Parameters
Response
Successful Response
⌘I