In order to provide a consistent and fully integrated experience for AWS developers that includes AWS Software Development Kit (SDK) support, we will be deprecating the legacy Requester APIs and final support will end on June 1, 2019. If you are still leveraging a legacy API, plan on migrating to the latest Requester API (version: ‘2017–01–17’) prior to then.



The latest version of the API ('2017-01-17') provides you with additional tool choices and enables you to select from nine AWS Software Development Kits (SDKs) that have been widely adopted across the AWS community. This API can be accessed using the following AWS SDKs: Python/Boto (Boto3), Javascript (NodeJS or Browser), Java, .NET, Go, Ruby, PHP or C++. This version also makes it easier for customers to connect MTurk with AWS services like S3, Lambda, Step Functions, Lex, Polly, Rekognition, Amazon Sagemaker, AWS Batch, EC2, and more.

This version also updates naming conventions used in the API and adopts the AWS standard of Signature Version 4 to authenticate requests securely. The API uses REST requests and no longer requires that developers be familiar with the SOAP protocol. These changes make the MTurk API consistent with AWS APIs, simplifying the on-boarding process for both new and existing AWS developers. The legacy MTurk Command Line Tools and .NET, Java, Ruby, and Perl SDKs were marked as deprecated in January 2018. We will be deprecating the legacy APIs as of June 1, 2019.



If you are on a legacy API, you must migrate to the latest version of our API prior to June 1, 2019. You can find the documentation for the latest API here and the AWS SDKs here. Please check whether you need to migrate and review the technical migration guide here.

If you request against a legacy API version on or after June 1, 2019, you will receive the following response: