What is Polymarket RTDS?

Changing the WebSocket URL alone does not migrate a client. PolyBolt changes authentication, op-based subscription messages, object filters, symbols and heartbeats. Its crypto spot source is Pyth; a USD reference series is not the old Binance USDT quote series.

Read full_accuracy_value as a decimal string, without the legacy E18 conversion. Preserve subscription snapshots and sequence continuity, and account for retired channels: the old 30-second TWAP has no listed replacement, while live comments are being retired and comment lists remain in REST.

Who it is for

Developers maintaining legacy RTDS clients.
Crypto and equity applications using reference prices.
Teams updating real-time data connections.

Features and coverage

Legacy activity topic
Keep activity on RTDS; PolyBolt has no replacement activity channel.
Reference-price channels
Use price.crypto and price.equity for supported spot references.
60-second TWAP
The Chainlink 60-second path maps to price.crypto.twap with window_seconds=60.
Authenticated prices
Send CLOB credentials in an auth message before subscribing.
Snapshots and sequences
Process the snapshot flag and per-channel sequence on subscription.
Connection health
Handle protocol Ping/Pong, dropped counters, reconnects and close codes.

Workflows with Polymarket RTDS

Migrate reference prices

Identify the old topic, authenticate to PolyBolt, choose a supported channel and lowercase USD symbol, then parse full_accuracy_value as a decimal string.

Maintain activity separately

Keep the RTDS activity connection while migrating prices and track both connection lifecycles.

Pricing and total cost

The migration guide lists no separate stream subscription price. Valid CLOB credentials are required for PolyBolt price channels.

Getting started

Before you start: The spot-price source changes to Pyth USD references.

Inventory the RTDS topics your application uses.
For prices, connect to wss://ws-live-v2.polymarket.com/ws.
Authenticate, then use op-based subscriptions and object filters.
Map btcusdt or btc/usd to btcusd; equity symbols are lowercase.
Handle snapshots, sequences, reconnects and closes; documented support needs @polymarket/client 0.11.0 or later.

Pyth USD references and Binance USDT quotes are different series.

Useful links

Polymarket Discord community

What to check

The spot-price source changes to Pyth USD references.
Do not apply E18 scaling to full_accuracy_value.
No replacement is listed for legacy 30-second TWAP.
Live comments retire without a replacement stream; REST comment listings remain.
PolyBolt allows 64 active subscriptions and 20 subscribe frames/second; violations can close the connection.

A closer look

Ratings & reviews

Editorial rating

3.0/ 5

0 user reviews

PredictionToolkit editorial

Our take on Polymarket RTDS

The migration guide supports maintaining real-time workflows. Changed sources and authentication, together with retired channels, require substantive updates to legacy clients.

Based on documented features, setup and access terms. How we rate

User reviews 0

The main score switches to user ratings after 5 published reviews.

Be the first to share your experience

A specific example helps the next person choose the right tool.

Related tools

Browse category

Frequently asked questions about Polymarket RTDS

Can I only change the endpoint?

No. Auth, op messages, filters, symbols and heartbeat handling change too.

Does every topic move to PolyBolt?

No. Activity stays on RTDS.

Which field preserves precision?

Read full_accuracy_value as a decimal string.

Why is btcusdt unsuitable?

The new crypto channel expects lowercase USD symbols such as btcusd.

Polymarket RTDS: separate activity from migrating price feeds

Screenshots and interface