What is Polymarket RTDS?
RTDS is Polymarket’s legacy real-time data service. Its activity topic remains on RTDS, while reference-price subscriptions are moving to PolyBolt. The distinction matters when maintaining an existing bot: changing only the WebSocket URL is insufficient because authentication, subscription messages, symbols and price encoding also change.
Who it is for
- Developers maintaining an RTDS integration
- Crypto and equity applications consuming reference prices
- Teams updating legacy market-data clients
Features and coverage
- Available on
- WebSocket
- Markets & venues
- Polymarket
- Research topics
- Crypto, Equities
- Activity stream
Continue using RTDS for the activity topic; PolyBolt has no replacement activity channel.
- Reference prices
Use PolyBolt price.crypto and price.equity for supported spot reference prices.
- TWAP prices
The 60-second Chainlink path maps to price.crypto.twap with window_seconds=60.
- Authenticated price access
PolyBolt requires CLOB credentials through an auth message before subscriptions.
- Subscription snapshots
Process the snapshot flag and per-channel sequence when establishing a subscription.
- Connection health
Handle protocol Ping/Pong, dropped counters and close codes in the new client.
Workflows with Polymarket RTDS
Migrate a crypto feed
Identify the legacy topic, authenticate to PolyBolt and map it to a supported channel. Convert symbols to lowercase USD pairs and read full_accuracy_value as a decimal string.
Keep an activity integration working
Retain the RTDS activity connection while migrating only the price subscriptions. Track the two connection lifecycles separately.
Pricing and total cost
No separate stream subscription price is listed in the migration guide. PolyBolt price channels require valid CLOB credentials.
Getting started
Before you start: The new crypto spot source is Pyth; a Binance USDT quote and a USD reference are not the same series.
- Inventory the RTDS topics used by the application.
- For prices, connect to wss://ws-live-v2.polymarket.com/ws.
- Authenticate, then send the documented op-based subscription with an object filter.
- Map btcusdt or btc/usd to btcusd; use lowercase equity symbols.
- Handle snapshots, sequence continuity, reconnects and close codes.
- Use @polymarket/client 0.11.0 or later for the documented PolyBolt support.
Useful links
What to check
- The new crypto spot source is Pyth; a Binance USDT quote and a USD reference are not the same series.
- Do not apply the old E18 fixed-point conversion to full_accuracy_value.
- The legacy 30-second TWAP has no listed replacement.
- Live comments are being retired without a replacement stream; comment listings remain available through REST.
- PolyBolt allows 64 active subscriptions and 20 subscribe frames per second; policy violations can close the connection.
A closer look
Ratings & reviews
User reviews 0
The main score switches to user ratings after 5 published reviews.
A specific example helps the next person choose the right tool.
Write a review
How was your experience with Polymarket RTDS?
Share what you used, what worked and what could be better. We confirm your email and review the submission before publishing.
To submit a review, email info@polytradingbot.com with the tool name, your rating and your experience. Enable JavaScript to prepare a draft here.
Related tools
Browse categoryFrequently asked questions about Polymarket RTDS
Can I replace the endpoint and keep the old messages?
No. Authentication, op fields, filters, symbols and heartbeat handling change.
Does all RTDS traffic migrate to PolyBolt?
No. The activity topic stays on RTDS.
Which price field preserves precision?
Parse full_accuracy_value as a decimal string.
Why does btcusdt fail?
The new crypto channel expects lowercase USD symbols such as btcusd.


