Product updates as they ship.
Bots that follow every market in a tournament can subscribe to one channel, tournament:{tournament_id}:markets, instead of one per market. Each markets_batch message carries the batches of markets that changed, with the same books and revisions as the per-market channels, which keep working.
Market lists, prices, trades and tournament details from the API may now be up to 2 seconds old, and order books up to 1 second old. Polling these faster than that returns the same data and still counts against your rate limit, so poll no more often than that.
Executed trades exports now include the price of the previous trade on the same market, so trades far from the going price stand out.
Realtime batches that can't be delivered promptly are now dropped instead of arriving late. When a batch's previousRevision is greater than the last revision you accepted, re-fetch the affected data over the REST API before acting on it. Because the last update before a quiet spell can be lost without a gap to show it, also refresh your state periodically, for example every one to two minutes.
Every Realtime channel, including the market, combined market, leaderboard and global violation channels, now requires the token from POST /api/v1/realtime/token, applied with setAuth before subscribing; a join without it is refused. When the server refuses a join, remove the channel instead of letting your client retry it, as shown in the Realtime section of the API reference.
Admin > Analytics now opens on a tournament's competition standings: every trader ranked by account value, with P&L, return, and their change over today, the week, or the month, filterable by user group and exportable to CSV. The previous Smart Score view is still available under "Trader signals".
Executed trades, orders and the transactions ledger are now prepared in the background from Admin > Export, so even very large exports finish reliably; each one downloads as a single compressed CSV file that stays available for 7 days. Trade exports now also show which side initiated each trade.
Participants who choose India when registering for the Predictions Cup now also select their state or union territory; residents of Andhra Pradesh, Telangana, Nagaland, Sikkim and Puducherry are not eligible. Participants already registered from India must choose theirs on the site before they can keep trading or using their API keys.
Scripts and bots should read market data through the API reference, using an API key from your profile: it covers bulk prices, price history and live updates. The docs explain how markets work. Automated requests to the website's own endpoints may be blocked.
Each account now has one API rate budget shared by all of its keys: 100 reads and 30 writes a minute, or 600 and 200 for DMM accounts. Creating more keys no longer adds capacity. Use bulk endpoints such as /api/v1/exchanges/prices, which accepts up to 100 exchange IDs per call, to stay within your budget.
