PolymarketPolymarket Gamma API Quote (outcomePrices) Issue Environment: Automated trading bot for 5-minute/15-minute crypto up/down binary markets. The bot queries the market via gamma-api.polymarket.com/events/slug/{slug} to retrieve the token_id and quotes (outcomePrices) to determine whether to enter a trade. Before migration (normal) The gamma /events/slug/ response included outcomePrices (Up/Down quotes) as actual market values. One market query = simultaneous retrieval of token_id and real-time quotes. Entry decisions could be made immediately without additional API calls → fast. Running multiple instances simultaneously was also lightweight. After Migration (Issue Occurred, Around June 12) outcomePrices began returning the fixed value [“0.5”, “0.5”] (fake data) instead of actual market data. Market metadata (token_id, slug, endDate, etc.) was normal, but only the quote fields were stuck at 0.5/0.5. It is impossible to make entry decisions (price comparisons) with these 0.5/0.5 values. Our attempted solutions CLOB /book REST polling — Since outcomePrices was down, we queried quotes separately via CLOB GET /book. However, this resulted in hundreds of calls per asset × side at each revaluation interval (0.3 seconds) → rate limiter serial queue congestion → overall latency (lag). CLOB Market Channel WebSocket (wss://ws-subscriptions-clob.polymarket.com/ws/market) — Subscribed to best_ask via push. Although REST polling has been eliminated, separating market queries (gamma) and quotes (WS) has introduced a time lag between subscribing and receiving the first quote for each new window → the immediacy of “simultaneous query and quote” from before the migration is lost. Current Key Issues (Questions for the Polymarket Team) Is the fact that `outcomePrices` in `gamma /events/slug/` returns dummy values of 0.5/0.5 an intended change, a bug, or a transitional issue? Is a fix planned? If so, when?
Polymarket Gamma API Quote (outcomePrices) Issue Environment: Automated trading bot for 5-minute/15-minute crypto up/down binary markets. The bot queries the market via gamma-api.polymarket.com/events/slug/{slug} to retrieve the token_id and quotes (outcomePrices) to determine whether to enter a trade. Before migration (normal) The gamma /events/slug/ response included outcomePrices (Up/Down quotes) as actual market values. One market query = simultaneous retrieval of token_id and real-time quotes. Entry decisions could be made immediately without additional API calls → fast. Running multiple instances simultaneously was also lightweight. After Migration (Issue Occurred, Around June 12) outcomePrices began returning the fixed value [“0.5”, “0.5”] (fake data) instead of actual market data. Market metadata (token_id, slug, endDate, etc.) was normal, but only the quote fields were stuck at 0.5/0.5. It is impossible to make entry decisions (price comparisons) with these 0.5/0.5 values. Our attempted solutions CLOB /book REST polling — Since outcomePrices was down, we queried quotes separately via CLOB GET /book. However, this resulted in hundreds of calls per asset × side at each revaluation interval (0.3 seconds) → rate limiter serial queue congestion → overall latency (lag). CLOB Market Channel WebSocket (wss://ws-subscriptions-clob.polymarket.com/ws/market) — Subscribed to best_ask via push. Although REST polling has been eliminated, separating market queries (gamma) and quotes (WS) has introduced a time lag between subscribing and receiving the first quote for each new window → the immediacy of “simultaneous query and quote” from before the migration is lost. Current Key Issues (Questions for the Polymarket Team) Is the fact that `outcomePrices` in `gamma /events/slug/` returns dummy values of 0.5/0.5 an intended change, a bug, or a transitional issue? Is a fix planned? If so, when?