tl;dr MTurk Suite (MTS) has been updated to function with TurkerView's new View API [details here] Everyone will need an API Key starting Feb 1 Feb 7 in order to use TV with MTS. They can be claimed here for free. Delayed cutoffs by a week due to time constraints in getting the push out to Kada. The first month is free for every user. Once that first month ends the price is discounted at $5/month for users that sign up before Feb 1 Feb 7 and $7.99/month otherwise. NOTE: If you have submitted at least 10 reviews on TV (as of 1/20/19), you will get a permanent key for free, this covers hundreds of users who helped build TV & is also extended to a # of community members who have contributed their time/expertise elsewhere. MTS now has more reliable access to TV's dataset, meaning about a 40% increase in coverage across the board from less failed requests/etc as well as new features that right now only exist in MTS! Improvements Requester Ratings MTS's on-page requester popovers are now designed with ease of access in mind. We want workers to be able to check data at a glance, and these should go a long way in facilitating that: Individual HIT Ratings TV will also send MTS data about individual HITs on the MTurk website: Task Results We've added two new task result APIs for MTS users: Advanced Task Breakdowns Advanced Task Breakdowns will show users more detailed results for individual HITs so they can get a more accurate idea of how long the task might take them. Leaving reviews on TV yourself greatly increases the usefulness of this tool so we highly recommend installing TVJS and reviewing HITs you complete! You can learn more about how to review on TV here. Real-Time Return Warnings Want to avoid broken HITs, unpaid screeners, and requesters who waste your time & violate MTurk's TOS? Get real time warning alerts through TV's Return Review system! HIT Finder HIT Finder has received the same love as on-page popups & now has live access to TurkerView! View API Load Testing / Optimization: TV's API should be pretty elastic, and I added some additional resources with the expectation adding MTS would be a significant load increase, however there are many aspects of the servers/infrastructure I cannot optimize until I see just how it responds to all 3 main services (TVJS, MTS, & Forker) being on the same endpoint. This small window of time before Feb 1st is probably my last chance to test this kind of stuff, and I'll be measuring the API with a few monitoring services, but I'd also like user feedback. If you see this in TVJS: Please let me know by simply sending me a message w/ the time! It shouldn't happen often (and if it does, it shouldn't take me more than an hour to throw up more servers to handle it) but I'll be using this week to get a clearer idea of what the usage:resource ratio is really like before problems occur.