Product updates as they ship.
Organization admins can now ban and unban their members in bulk from the new Bans tab, by pasting or uploading a list of usernames, and email them using editable ban and unban templates. Banned accounts are signed out and can no longer sign in; they see a suspension message instead.
When a request briefly collides with other activity on the same data, the API now returns a retryable 503 TX_CONFLICT with a Retry-After header instead of a 500 error. Wait for the Retry-After delay, then retry with backoff. Temporary trading engine or admission unavailability is now reported as SERVICE_UNAVAILABLE rather than TX_CONFLICT.
A phone number is now reserved for the first Predictions Cup account that confirms its email. If you registered with a mistyped email address, you can register again with the same phone number.
When someone joins a tournament, whether they sign up, are added by an admin or through the API, or join with an invite code, their starting balance is now ready before the request finishes. Admin and API member lists and rankings no longer briefly fail just after someone joins.
Predictions Cup registration now texts a code to your mobile number, which you enter to finish signing up. Internet and landline numbers can't receive codes, so register with a mobile number.
New Predictions Cup registrations from the United States need a university email address ending in .edu, and the sign-up form says so as soon as you choose the United States. Participants who live elsewhere can register with any email address.
Each phone number can now be used for only one Predictions Cup registration. Registering again with a number that is already linked to an account is turned away, and the sign-up form shows why under the phone number field.
The tournament portfolio chart's 1 Day and 1 Week views now show your value hour by hour, with 1 Week points labelled by their hour, and the 1 Month view shows how it changed within each day instead of once a day. In the API, tournament portfolio history at the 1h and 6h intervals now returns these hourly values for the last 31 days.
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.
