API Reference

List Updown Intervals

Get updown markets organized by interval with rotation timing metadata. Designed for trading bots that need to: 1. Know which markets are currently active per interval 2. See how much time remains before the current interval expires 3. Discover the next interval's markets to rotate into Returns a dict keyed by interval (1H, 4H, daily, etc.) with: - current: list of active markets for this interval (end_date in the future) - seconds_until_rotation: seconds until the soonest market in this interval expires - next_rotation_at: ISO timestamp of when the soonest market expires - asset_markets: nested {asset: [markets]} for quick lookup

GET

markets

updown

intervals

List Updown Intervals

curl --request GET \
  --url https://api.polysimulator.com/v1/markets/updown/intervals

{
  "intervals": {},
  "available_intervals": [
    "<string>"
  ],
  "total_markets": 123,
  "crypto_prices": {},
  "timestamp": "<string>"
}

Query Parameters

asset

string | null

Filter by asset: BTC, ETH, SOL, XRP, SPX, NDX

Response

Successful Response

intervals

object

available_intervals

string[]

total_markets

integer

crypto_prices

object

timestamp

string

Preview AlertRender a single (event_type, channel) preview using the production formatters. Auth-scoped — only the caller's own most-recent wallet trade is used as sample data, and only when ``wallet_address`` is in their ``tracked_wallets`` set. The endpoint NEVER sends a real alert — it only renders. Use the existing per-channel ``/me/<channel>/test`` POST endpoints to send a real test.

List Updown Intervals

curl --request GET \
  --url https://api.polysimulator.com/v1/markets/updown/intervals

{
  "intervals": {},
  "available_intervals": [
    "<string>"
  ],
  "total_markets": 123,
  "crypto_prices": {},
  "timestamp": "<string>"
}