1{
2  "version": "2.0",
3  "service": "<fullname>Amazon Mechanical Turk API Reference</fullname>",
4  "operations": {
5    "AcceptQualificationRequest": "<p> The <code>AcceptQualificationRequest</code> operation approves a Worker's request for a Qualification. </p> <p> Only the owner of the Qualification type can grant a Qualification request for that type. </p> <p> A successful request for the <code>AcceptQualificationRequest</code> operation returns with no errors and an empty body. </p>",
6    "ApproveAssignment": "<p> The <code>ApproveAssignment</code> operation approves the results of a completed assignment. </p> <p> Approving an assignment initiates two payments from the Requester's Amazon.com account </p> <ul> <li> <p> The Worker who submitted the results is paid the reward specified in the HIT. </p> </li> <li> <p> Amazon Mechanical Turk fees are debited. </p> </li> </ul> <p> If the Requester's account does not have adequate funds for these payments, the call to ApproveAssignment returns an exception, and the approval is not processed. You can include an optional feedback message with the approval, which the Worker can see in the Status section of the web site. </p> <p> You can also call this operation for assignments that were previous rejected and approve them by explicitly overriding the previous rejection. This only works on rejected assignments that were submitted within the previous 30 days and only if the assignment's related HIT has not been deleted. </p>",
7    "AssociateQualificationWithWorker": "<p> The <code>AssociateQualificationWithWorker</code> operation gives a Worker a Qualification. <code>AssociateQualificationWithWorker</code> does not require that the Worker submit a Qualification request. It gives the Qualification directly to the Worker. </p> <p> You can only assign a Qualification of a Qualification type that you created (using the <code>CreateQualificationType</code> operation). </p> <note> <p> Note: <code>AssociateQualificationWithWorker</code> does not affect any pending Qualification requests for the Qualification by the Worker. If you assign a Qualification to a Worker, then later grant a Qualification request made by the Worker, the granting of the request may modify the Qualification score. To resolve a pending Qualification request without affecting the Qualification the Worker already has, reject the request with the <code>RejectQualificationRequest</code> operation. </p> </note>",
8    "CreateAdditionalAssignmentsForHIT": "<p> The <code>CreateAdditionalAssignmentsForHIT</code> operation increases the maximum number of assignments of an existing HIT. </p> <p> To extend the maximum number of assignments, specify the number of additional assignments.</p> <note> <ul> <li> <p>HITs created with fewer than 10 assignments cannot be extended to have 10 or more assignments. Attempting to add assignments in a way that brings the total number of assignments for a HIT from fewer than 10 assignments to 10 or more assignments will result in an <code>AWS.MechanicalTurk.InvalidMaximumAssignmentsIncrease</code> exception.</p> </li> <li> <p>HITs that were created before July 22, 2015 cannot be extended. Attempting to extend HITs that were created before July 22, 2015 will result in an <code>AWS.MechanicalTurk.HITTooOldForExtension</code> exception. </p> </li> </ul> </note>",
9    "CreateHIT": "<p>The <code>CreateHIT</code> operation creates a new Human Intelligence Task (HIT). The new HIT is made available for Workers to find and accept on the Amazon Mechanical Turk website. </p> <p> This operation allows you to specify a new HIT by passing in values for the properties of the HIT, such as its title, reward amount and number of assignments. When you pass these values to <code>CreateHIT</code>, a new HIT is created for you, with a new <code>HITTypeID</code>. The HITTypeID can be used to create additional HITs in the future without needing to specify common parameters such as the title, description and reward amount each time.</p> <p> An alternative way to create HITs is to first generate a HITTypeID using the <code>CreateHITType</code> operation and then call the <code>CreateHITWithHITType</code> operation. This is the recommended best practice for Requesters who are creating large numbers of HITs. </p> <p>CreateHIT also supports several ways to provide question data: by providing a value for the <code>Question</code> parameter that fully specifies the contents of the HIT, or by providing a <code>HitLayoutId</code> and associated <code>HitLayoutParameters</code>. </p> <note> <p> If a HIT is created with 10 or more maximum assignments, there is an additional fee. For more information, see <a href=\"https://requester.mturk.com/pricing\">Amazon Mechanical Turk Pricing</a>.</p> </note>",
10    "CreateHITType": "<p> The <code>CreateHITType</code> operation creates a new HIT type. This operation allows you to define a standard set of HIT properties to use when creating HITs. If you register a HIT type with values that match an existing HIT type, the HIT type ID of the existing type will be returned. </p>",
11    "CreateHITWithHITType": "<p> The <code>CreateHITWithHITType</code> operation creates a new Human Intelligence Task (HIT) using an existing HITTypeID generated by the <code>CreateHITType</code> operation. </p> <p> This is an alternative way to create HITs from the <code>CreateHIT</code> operation. This is the recommended best practice for Requesters who are creating large numbers of HITs. </p> <p>CreateHITWithHITType also supports several ways to provide question data: by providing a value for the <code>Question</code> parameter that fully specifies the contents of the HIT, or by providing a <code>HitLayoutId</code> and associated <code>HitLayoutParameters</code>. </p> <note> <p> If a HIT is created with 10 or more maximum assignments, there is an additional fee. For more information, see <a href=\"https://requester.mturk.com/pricing\">Amazon Mechanical Turk Pricing</a>. </p> </note>",
12    "CreateQualificationType": "<p> The <code>CreateQualificationType</code> operation creates a new Qualification type, which is represented by a <code>QualificationType</code> data structure. </p>",
13    "CreateWorkerBlock": "<p>The <code>CreateWorkerBlock</code> operation allows you to prevent a Worker from working on your HITs. For example, you can block a Worker who is producing poor quality work. You can block up to 100,000 Workers.</p>",
14    "DeleteHIT": "<p> The <code>DeleteHIT</code> operation is used to delete HIT that is no longer needed. Only the Requester who created the HIT can delete it. </p> <p> You can only dispose of HITs that are in the <code>Reviewable</code> state, with all of their submitted assignments already either approved or rejected. If you call the DeleteHIT operation on a HIT that is not in the <code>Reviewable</code> state (for example, that has not expired, or still has active assignments), or on a HIT that is Reviewable but without all of its submitted assignments already approved or rejected, the service will return an error. </p> <note> <ul> <li> <p> HITs are automatically disposed of after 120 days. </p> </li> <li> <p> After you dispose of a HIT, you can no longer approve the HIT's rejected assignments. </p> </li> <li> <p> Disposed HITs are not returned in results for the ListHITs operation. </p> </li> <li> <p> Disposing HITs can improve the performance of operations such as ListReviewableHITs and ListHITs. </p> </li> </ul> </note>",
15    "DeleteQualificationType": "<p> The <code>DeleteQualificationType</code> deletes a Qualification type and deletes any HIT types that are associated with the Qualification type. </p> <p>This operation does not revoke Qualifications already assigned to Workers because the Qualifications might be needed for active HITs. If there are any pending requests for the Qualification type, Amazon Mechanical Turk rejects those requests. After you delete a Qualification type, you can no longer use it to create HITs or HIT types.</p> <note> <p>DeleteQualificationType must wait for all the HITs that use the deleted Qualification type to be deleted before completing. It may take up to 48 hours before DeleteQualificationType completes and the unique name of the Qualification type is available for reuse with CreateQualificationType.</p> </note>",
16    "DeleteWorkerBlock": "<p>The <code>DeleteWorkerBlock</code> operation allows you to reinstate a blocked Worker to work on your HITs. This operation reverses the effects of the CreateWorkerBlock operation. You need the Worker ID to use this operation. If the Worker ID is missing or invalid, this operation fails and returns the message “WorkerId is invalid.” If the specified Worker is not blocked, this operation returns successfully.</p>",
17    "DisassociateQualificationFromWorker": "<p> The <code>DisassociateQualificationFromWorker</code> revokes a previously granted Qualification from a user. </p> <p> You can provide a text message explaining why the Qualification was revoked. The user who had the Qualification can see this message. </p>",
18    "GetAccountBalance": "<p>The <code>GetAccountBalance</code> operation retrieves the Prepaid HITs balance in your Amazon Mechanical Turk account if you are a Prepaid Requester. Alternatively, this operation will retrieve the remaining available AWS Billing usage if you have enabled AWS Billing. Note: If you have enabled AWS Billing and still have a remaining Prepaid HITs balance, this balance can be viewed on the My Account page in the Requester console.</p>",
19    "GetAssignment": "<p> The <code>GetAssignment</code> operation retrieves the details of the specified Assignment. </p>",
20    "GetFileUploadURL": "<p> The <code>GetFileUploadURL</code> operation generates and returns a temporary URL. You use the temporary URL to retrieve a file uploaded by a Worker as an answer to a FileUploadAnswer question for a HIT. The temporary URL is generated the instant the GetFileUploadURL operation is called, and is valid for 60 seconds. You can get a temporary file upload URL any time until the HIT is disposed. After the HIT is disposed, any uploaded files are deleted, and cannot be retrieved. Pending Deprecation on December 12, 2017. The Answer Specification structure will no longer support the <code>FileUploadAnswer</code> element to be used for the QuestionForm data structure. Instead, we recommend that Requesters who want to create HITs asking Workers to upload files to use Amazon S3. </p>",
21    "GetHIT": "<p> The <code>GetHIT</code> operation retrieves the details of the specified HIT. </p>",
22    "GetQualificationScore": "<p> The <code>GetQualificationScore</code> operation returns the value of a Worker's Qualification for a given Qualification type. </p> <p> To get a Worker's Qualification, you must know the Worker's ID. The Worker's ID is included in the assignment data returned by the <code>ListAssignmentsForHIT</code> operation. </p> <p>Only the owner of a Qualification type can query the value of a Worker's Qualification of that type.</p>",
23    "GetQualificationType": "<p> The <code>GetQualificationType</code>operation retrieves information about a Qualification type using its ID. </p>",
24    "ListAssignmentsForHIT": "<p> The <code>ListAssignmentsForHIT</code> operation retrieves completed assignments for a HIT. You can use this operation to retrieve the results for a HIT. </p> <p> You can get assignments for a HIT at any time, even if the HIT is not yet Reviewable. If a HIT requested multiple assignments, and has received some results but has not yet become Reviewable, you can still retrieve the partial results with this operation. </p> <p> Use the AssignmentStatus parameter to control which set of assignments for a HIT are returned. The ListAssignmentsForHIT operation can return submitted assignments awaiting approval, or it can return assignments that have already been approved or rejected. You can set AssignmentStatus=Approved,Rejected to get assignments that have already been approved and rejected together in one result set. </p> <p> Only the Requester who created the HIT can retrieve the assignments for that HIT. </p> <p> Results are sorted and divided into numbered pages and the operation returns a single page of results. You can use the parameters of the operation to control sorting and pagination. </p>",
25    "ListBonusPayments": "<p> The <code>ListBonusPayments</code> operation retrieves the amounts of bonuses you have paid to Workers for a given HIT or assignment. </p>",
26    "ListHITs": "<p> The <code>ListHITs</code> operation returns all of a Requester's HITs. The operation returns HITs of any status, except for HITs that have been deleted of with the DeleteHIT operation or that have been auto-deleted. </p>",
27    "ListHITsForQualificationType": "<p> The <code>ListHITsForQualificationType</code> operation returns the HITs that use the given Qualification type for a Qualification requirement. The operation returns HITs of any status, except for HITs that have been deleted with the <code>DeleteHIT</code> operation or that have been auto-deleted. </p>",
28    "ListQualificationRequests": "<p> The <code>ListQualificationRequests</code> operation retrieves requests for Qualifications of a particular Qualification type. The owner of the Qualification type calls this operation to poll for pending requests, and accepts them using the AcceptQualification operation. </p>",
29    "ListQualificationTypes": "<p> The <code>ListQualificationTypes</code> operation returns a list of Qualification types, filtered by an optional search term. </p>",
30    "ListReviewPolicyResultsForHIT": "<p> The <code>ListReviewPolicyResultsForHIT</code> operation retrieves the computed results and the actions taken in the course of executing your Review Policies for a given HIT. For information about how to specify Review Policies when you call CreateHIT, see Review Policies. The ListReviewPolicyResultsForHIT operation can return results for both Assignment-level and HIT-level review results. </p>",
31    "ListReviewableHITs": "<p> The <code>ListReviewableHITs</code> operation retrieves the HITs with Status equal to Reviewable or Status equal to Reviewing that belong to the Requester calling the operation. </p>",
32    "ListWorkerBlocks": "<p>The <code>ListWorkersBlocks</code> operation retrieves a list of Workers who are blocked from working on your HITs.</p>",
33    "ListWorkersWithQualificationType": "<p> The <code>ListWorkersWithQualificationType</code> operation returns all of the Workers that have been associated with a given Qualification type. </p>",
34    "NotifyWorkers": "<p> The <code>NotifyWorkers</code> operation sends an email to one or more Workers that you specify with the Worker ID. You can specify up to 100 Worker IDs to send the same message with a single call to the NotifyWorkers operation. The NotifyWorkers operation will send a notification email to a Worker only if you have previously approved or rejected work from the Worker. </p>",
35    "RejectAssignment": "<p> The <code>RejectAssignment</code> operation rejects the results of a completed assignment. </p> <p> You can include an optional feedback message with the rejection, which the Worker can see in the Status section of the web site. When you include a feedback message with the rejection, it helps the Worker understand why the assignment was rejected, and can improve the quality of the results the Worker submits in the future. </p> <p> Only the Requester who created the HIT can reject an assignment for the HIT. </p>",
36    "RejectQualificationRequest": "<p> The <code>RejectQualificationRequest</code> operation rejects a user's request for a Qualification. </p> <p> You can provide a text message explaining why the request was rejected. The Worker who made the request can see this message.</p>",
37    "SendBonus": "<p> The <code>SendBonus</code> operation issues a payment of money from your account to a Worker. This payment happens separately from the reward you pay to the Worker when you approve the Worker's assignment. The SendBonus operation requires the Worker's ID and the assignment ID as parameters to initiate payment of the bonus. You must include a message that explains the reason for the bonus payment, as the Worker may not be expecting the payment. Amazon Mechanical Turk collects a fee for bonus payments, similar to the HIT listing fee. This operation fails if your account does not have enough funds to pay for both the bonus and the fees. </p>",
38    "SendTestEventNotification": "<p> The <code>SendTestEventNotification</code> operation causes Amazon Mechanical Turk to send a notification message as if a HIT event occurred, according to the provided notification specification. This allows you to test notifications without setting up notifications for a real HIT type and trying to trigger them using the website. When you call this operation, the service attempts to send the test notification immediately. </p>",
39    "UpdateExpirationForHIT": "<p> The <code>UpdateExpirationForHIT</code> operation allows you update the expiration time of a HIT. If you update it to a time in the past, the HIT will be immediately expired. </p>",
40    "UpdateHITReviewStatus": "<p> The <code>UpdateHITReviewStatus</code> operation updates the status of a HIT. If the status is Reviewable, this operation can update the status to Reviewing, or it can revert a Reviewing HIT back to the Reviewable status. </p>",
41    "UpdateHITTypeOfHIT": "<p> The <code>UpdateHITTypeOfHIT</code> operation allows you to change the HITType properties of a HIT. This operation disassociates the HIT from its old HITType properties and associates it with the new HITType properties. The HIT takes on the properties of the new HITType in place of the old ones. </p>",
42    "UpdateNotificationSettings": "<p> The <code>UpdateNotificationSettings</code> operation creates, updates, disables or re-enables notifications for a HIT type. If you call the UpdateNotificationSettings operation for a HIT type that already has a notification specification, the operation replaces the old specification with a new one. You can call the UpdateNotificationSettings operation to enable or disable notifications for the HIT type, without having to modify the notification specification itself by providing updates to the Active status without specifying a new notification specification. To change the Active status of a HIT type's notifications, the HIT type must already have a notification specification, or one must be provided in the same call to <code>UpdateNotificationSettings</code>. </p>",
43    "UpdateQualificationType": "<p> The <code>UpdateQualificationType</code> operation modifies the attributes of an existing Qualification type, which is represented by a QualificationType data structure. Only the owner of a Qualification type can modify its attributes. </p> <p> Most attributes of a Qualification type can be changed after the type has been created. However, the Name and Keywords fields cannot be modified. The RetryDelayInSeconds parameter can be modified or added to change the delay or to enable retries, but RetryDelayInSeconds cannot be used to disable retries. </p> <p> You can use this operation to update the test for a Qualification type. The test is updated based on the values specified for the Test, TestDurationInSeconds and AnswerKey parameters. All three parameters specify the updated test. If you are updating the test for a type, you must specify the Test and TestDurationInSeconds parameters. The AnswerKey parameter is optional; omitting it specifies that the updated test does not have an answer key. </p> <p> If you omit the Test parameter, the test for the Qualification type is unchanged. There is no way to remove a test from a Qualification type that has one. If the type already has a test, you cannot update it to be AutoGranted. If the Qualification type does not have a test and one is provided by an update, the type will henceforth have a test. </p> <p> If you want to update the test duration or answer key for an existing test without changing the questions, you must specify a Test parameter with the original questions, along with the updated values. </p> <p> If you provide an updated Test but no AnswerKey, the new test will not have an answer key. Requests for such Qualifications must be granted manually. </p> <p> You can also update the AutoGranted and AutoGrantedValue attributes of the Qualification type.</p>"
44  },
45  "shapes": {
46    "AcceptQualificationRequestRequest": {
47      "base": null,
48      "refs": {
49      }
50    },
51    "AcceptQualificationRequestResponse": {
52      "base": null,
53      "refs": {
54      }
55    },
56    "ApproveAssignmentRequest": {
57      "base": null,
58      "refs": {
59      }
60    },
61    "ApproveAssignmentResponse": {
62      "base": null,
63      "refs": {
64      }
65    },
66    "Assignment": {
67      "base": "<p> The Assignment data structure represents a single assignment of a HIT to a Worker. The assignment tracks the Worker's efforts to complete the HIT, and contains the results for later retrieval. </p>",
68      "refs": {
69        "AssignmentList$member": null,
70        "GetAssignmentResponse$Assignment": "<p> The assignment. The response includes one Assignment element. </p>"
71      }
72    },
73    "AssignmentList": {
74      "base": null,
75      "refs": {
76        "ListAssignmentsForHITResponse$Assignments": "<p> The collection of Assignment data structures returned by this call.</p>"
77      }
78    },
79    "AssignmentStatus": {
80      "base": null,
81      "refs": {
82        "Assignment$AssignmentStatus": "<p> The status of the assignment.</p>",
83        "AssignmentStatusList$member": null
84      }
85    },
86    "AssignmentStatusList": {
87      "base": null,
88      "refs": {
89        "ListAssignmentsForHITRequest$AssignmentStatuses": "<p>The status of the assignments to return: Submitted | Approved | Rejected</p>"
90      }
91    },
92    "AssociateQualificationWithWorkerRequest": {
93      "base": null,
94      "refs": {
95      }
96    },
97    "AssociateQualificationWithWorkerResponse": {
98      "base": null,
99      "refs": {
100      }
101    },
102    "BonusPayment": {
103      "base": "<p>An object representing a Bonus payment paid to a Worker.</p>",
104      "refs": {
105        "BonusPaymentList$member": null
106      }
107    },
108    "BonusPaymentList": {
109      "base": null,
110      "refs": {
111        "ListBonusPaymentsResponse$BonusPayments": "<p>A successful request to the ListBonusPayments operation returns a list of BonusPayment objects. </p>"
112      }
113    },
114    "Boolean": {
115      "base": null,
116      "refs": {
117        "ApproveAssignmentRequest$OverrideRejection": "<p> A flag indicating that an assignment should be approved even if it was previously rejected. Defaults to <code>False</code>. </p>",
118        "AssociateQualificationWithWorkerRequest$SendNotification": "<p> Specifies whether to send a notification email message to the Worker saying that the qualification was assigned to the Worker. Note: this is true by default. </p>",
119        "CreateQualificationTypeRequest$AutoGranted": "<p>Specifies whether requests for the Qualification type are granted immediately, without prompting the Worker with a Qualification test.</p> <p>Constraints: If the Test parameter is specified, this parameter cannot be true.</p>",
120        "ListQualificationTypesRequest$MustBeRequestable": "<p>Specifies that only Qualification types that a user can request through the Amazon Mechanical Turk web site, such as by taking a Qualification test, are returned as results of the search. Some Qualification types, such as those assigned automatically by the system, cannot be requested directly by users. If false, all Qualification types, including those managed by the system, are considered. Valid values are True | False. </p>",
121        "ListQualificationTypesRequest$MustBeOwnedByCaller": "<p> Specifies that only Qualification types that the Requester created are returned. If false, the operation returns all Qualification types. </p>",
122        "ListReviewPolicyResultsForHITRequest$RetrieveActions": "<p> Specify if the operation should retrieve a list of the actions taken executing the Review Policies and their outcomes. </p>",
123        "ListReviewPolicyResultsForHITRequest$RetrieveResults": "<p> Specify if the operation should retrieve a list of the results computed by the Review Policies. </p>",
124        "QualificationRequirement$RequiredToPreview": "<p> DEPRECATED: Use the <code>ActionsGuarded</code> field instead. If RequiredToPreview is true, the question data for the HIT will not be shown when a Worker whose Qualifications do not meet this requirement tries to preview the HIT. That is, a Worker's Qualifications must meet all of the requirements for which RequiredToPreview is true in order to preview the HIT. If a Worker meets all of the requirements where RequiredToPreview is true (or if there are no such requirements), but does not meet all of the requirements for the HIT, the Worker will be allowed to preview the HIT's question data, but will not be allowed to accept and complete the HIT. The default is false. This should not be used in combination with the <code>ActionsGuarded</code> field. </p>",
125        "QualificationType$IsRequestable": "<p> Specifies whether the Qualification type is one that a user can request through the Amazon Mechanical Turk web site, such as by taking a Qualification test. This value is False for Qualifications assigned automatically by the system. Valid values are True | False. </p>",
126        "QualificationType$AutoGranted": "<p>Specifies that requests for the Qualification type are granted immediately, without prompting the Worker with a Qualification test. Valid values are True | False.</p>",
127        "UpdateHITReviewStatusRequest$Revert": "<p> Specifies how to update the HIT status. Default is <code>False</code>. </p> <ul> <li> <p> Setting this to false will only transition a HIT from <code>Reviewable</code> to <code>Reviewing</code> </p> </li> <li> <p> Setting this to true will only transition a HIT from <code>Reviewing</code> to <code>Reviewable</code> </p> </li> </ul>",
128        "UpdateNotificationSettingsRequest$Active": "<p> Specifies whether notifications are sent for HITs of this HIT type, according to the notification specification. You must specify either the Notification parameter or the Active parameter for the call to UpdateNotificationSettings to succeed. </p>",
129        "UpdateQualificationTypeRequest$AutoGranted": "<p>Specifies whether requests for the Qualification type are granted immediately, without prompting the Worker with a Qualification test.</p> <p>Constraints: If the Test parameter is specified, this parameter cannot be true.</p>"
130      }
131    },
132    "Comparator": {
133      "base": null,
134      "refs": {
135        "QualificationRequirement$Comparator": "<p>The kind of comparison to make against a Qualification's value. You can compare a Qualification's value to an IntegerValue to see if it is LessThan, LessThanOrEqualTo, GreaterThan, GreaterThanOrEqualTo, EqualTo, or NotEqualTo the IntegerValue. You can compare it to a LocaleValue to see if it is EqualTo, or NotEqualTo the LocaleValue. You can check to see if the value is In or NotIn a set of IntegerValue or LocaleValue values. Lastly, a Qualification requirement can also test if a Qualification Exists or DoesNotExist in the user's profile, regardless of its value. </p>"
136      }
137    },
138    "CountryParameters": {
139      "base": null,
140      "refs": {
141        "Locale$Country": "<p> The country of the locale. Must be a valid ISO 3166 country code. For example, the code US refers to the United States of America. </p>",
142        "Locale$Subdivision": "<p>The state or subdivision of the locale. A valid ISO 3166-2 subdivision code. For example, the code WA refers to the state of Washington.</p>"
143      }
144    },
145    "CreateAdditionalAssignmentsForHITRequest": {
146      "base": null,
147      "refs": {
148      }
149    },
150    "CreateAdditionalAssignmentsForHITResponse": {
151      "base": null,
152      "refs": {
153      }
154    },
155    "CreateHITRequest": {
156      "base": null,
157      "refs": {
158      }
159    },
160    "CreateHITResponse": {
161      "base": null,
162      "refs": {
163      }
164    },
165    "CreateHITTypeRequest": {
166      "base": null,
167      "refs": {
168      }
169    },
170    "CreateHITTypeResponse": {
171      "base": null,
172      "refs": {
173      }
174    },
175    "CreateHITWithHITTypeRequest": {
176      "base": null,
177      "refs": {
178      }
179    },
180    "CreateHITWithHITTypeResponse": {
181      "base": null,
182      "refs": {
183      }
184    },
185    "CreateQualificationTypeRequest": {
186      "base": null,
187      "refs": {
188      }
189    },
190    "CreateQualificationTypeResponse": {
191      "base": null,
192      "refs": {
193      }
194    },
195    "CreateWorkerBlockRequest": {
196      "base": null,
197      "refs": {
198      }
199    },
200    "CreateWorkerBlockResponse": {
201      "base": null,
202      "refs": {
203      }
204    },
205    "CurrencyAmount": {
206      "base": "<p>A string representing a currency amount.</p>",
207      "refs": {
208        "BonusPayment$BonusAmount": null,
209        "CreateHITRequest$Reward": "<p> The amount of money the Requester will pay a Worker for successfully completing the HIT. </p>",
210        "CreateHITTypeRequest$Reward": "<p> The amount of money the Requester will pay a Worker for successfully completing the HIT. </p>",
211        "GetAccountBalanceResponse$AvailableBalance": null,
212        "GetAccountBalanceResponse$OnHoldBalance": null,
213        "HIT$Reward": null,
214        "SendBonusRequest$BonusAmount": "<p> The Bonus amount is a US Dollar amount specified using a string (for example, \"5\" represents $5.00 USD and \"101.42\" represents $101.42 USD). Do not include currency symbols or currency codes. </p>"
215      }
216    },
217    "CustomerId": {
218      "base": null,
219      "refs": {
220        "Assignment$WorkerId": "<p> The ID of the Worker who accepted the HIT.</p>",
221        "AssociateQualificationWithWorkerRequest$WorkerId": "<p> The ID of the Worker to whom the Qualification is being assigned. Worker IDs are included with submitted HIT assignments and Qualification requests. </p>",
222        "BonusPayment$WorkerId": "<p>The ID of the Worker to whom the bonus was paid.</p>",
223        "CreateWorkerBlockRequest$WorkerId": "<p>The ID of the Worker to block.</p>",
224        "CustomerIdList$member": null,
225        "DeleteWorkerBlockRequest$WorkerId": "<p>The ID of the Worker to unblock.</p>",
226        "DisassociateQualificationFromWorkerRequest$WorkerId": "<p>The ID of the Worker who possesses the Qualification to be revoked.</p>",
227        "GetQualificationScoreRequest$WorkerId": "<p>The ID of the Worker whose Qualification is being updated.</p>",
228        "NotifyWorkersFailureStatus$WorkerId": "<p> The ID of the Worker.</p>",
229        "Qualification$WorkerId": "<p> The ID of the Worker who possesses the Qualification. </p>",
230        "QualificationRequest$WorkerId": "<p> The ID of the Worker requesting the Qualification.</p>",
231        "SendBonusRequest$WorkerId": "<p>The ID of the Worker being paid the bonus.</p>",
232        "WorkerBlock$WorkerId": "<p> The ID of the Worker who accepted the HIT.</p>"
233      }
234    },
235    "CustomerIdList": {
236      "base": null,
237      "refs": {
238        "NotifyWorkersRequest$WorkerIds": "<p>A list of Worker IDs you wish to notify. You can notify upto 100 Workers at a time.</p>"
239      }
240    },
241    "DeleteHITRequest": {
242      "base": null,
243      "refs": {
244      }
245    },
246    "DeleteHITResponse": {
247      "base": null,
248      "refs": {
249      }
250    },
251    "DeleteQualificationTypeRequest": {
252      "base": null,
253      "refs": {
254      }
255    },
256    "DeleteQualificationTypeResponse": {
257      "base": null,
258      "refs": {
259      }
260    },
261    "DeleteWorkerBlockRequest": {
262      "base": null,
263      "refs": {
264      }
265    },
266    "DeleteWorkerBlockResponse": {
267      "base": null,
268      "refs": {
269      }
270    },
271    "DisassociateQualificationFromWorkerRequest": {
272      "base": null,
273      "refs": {
274      }
275    },
276    "DisassociateQualificationFromWorkerResponse": {
277      "base": null,
278      "refs": {
279      }
280    },
281    "EntityId": {
282      "base": null,
283      "refs": {
284        "ApproveAssignmentRequest$AssignmentId": "<p> The ID of the assignment. The assignment must correspond to a HIT created by the Requester. </p>",
285        "Assignment$AssignmentId": "<p> A unique identifier for the assignment.</p>",
286        "Assignment$HITId": "<p> The ID of the HIT.</p>",
287        "AssociateQualificationWithWorkerRequest$QualificationTypeId": "<p>The ID of the Qualification type to use for the assigned Qualification.</p>",
288        "BonusPayment$AssignmentId": "<p>The ID of the assignment associated with this bonus payment.</p>",
289        "CreateAdditionalAssignmentsForHITRequest$HITId": "<p>The ID of the HIT to extend.</p>",
290        "CreateHITRequest$HITLayoutId": "<p> The HITLayoutId allows you to use a pre-existing HIT design with placeholder values and create an additional HIT by providing those values as HITLayoutParameters. </p> <p> Constraints: Either a Question parameter or a HITLayoutId parameter must be provided. </p>",
291        "CreateHITTypeResponse$HITTypeId": "<p> The ID of the newly registered HIT type.</p>",
292        "CreateHITWithHITTypeRequest$HITTypeId": "<p>The HIT type ID you want to create this HIT with.</p>",
293        "CreateHITWithHITTypeRequest$HITLayoutId": "<p> The HITLayoutId allows you to use a pre-existing HIT design with placeholder values and create an additional HIT by providing those values as HITLayoutParameters. </p> <p> Constraints: Either a Question parameter or a HITLayoutId parameter must be provided. </p>",
294        "DeleteHITRequest$HITId": "<p>The ID of the HIT to be deleted.</p>",
295        "DeleteQualificationTypeRequest$QualificationTypeId": "<p>The ID of the QualificationType to dispose.</p>",
296        "DisassociateQualificationFromWorkerRequest$QualificationTypeId": "<p>The ID of the Qualification type of the Qualification to be revoked.</p>",
297        "GetAssignmentRequest$AssignmentId": "<p>The ID of the Assignment to be retrieved.</p>",
298        "GetFileUploadURLRequest$AssignmentId": "<p>The ID of the assignment that contains the question with a FileUploadAnswer.</p>",
299        "GetHITRequest$HITId": "<p>The ID of the HIT to be retrieved.</p>",
300        "GetQualificationScoreRequest$QualificationTypeId": "<p>The ID of the QualificationType.</p>",
301        "GetQualificationTypeRequest$QualificationTypeId": "<p>The ID of the QualificationType.</p>",
302        "HIT$HITId": "<p> A unique identifier for the HIT.</p>",
303        "HIT$HITTypeId": "<p>The ID of the HIT type of this HIT</p>",
304        "HIT$HITGroupId": "<p> The ID of the HIT Group of this HIT.</p>",
305        "HIT$HITLayoutId": "<p> The ID of the HIT Layout of this HIT.</p>",
306        "ListAssignmentsForHITRequest$HITId": "<p>The ID of the HIT.</p>",
307        "ListBonusPaymentsRequest$HITId": "<p>The ID of the HIT associated with the bonus payments to retrieve. If not specified, all bonus payments for all assignments for the given HIT are returned. Either the HITId parameter or the AssignmentId parameter must be specified</p>",
308        "ListBonusPaymentsRequest$AssignmentId": "<p>The ID of the assignment associated with the bonus payments to retrieve. If specified, only bonus payments for the given assignment are returned. Either the HITId parameter or the AssignmentId parameter must be specified</p>",
309        "ListHITsForQualificationTypeRequest$QualificationTypeId": "<p> The ID of the Qualification type to use when querying HITs. </p>",
310        "ListQualificationRequestsRequest$QualificationTypeId": "<p>The ID of the QualificationType.</p>",
311        "ListReviewPolicyResultsForHITRequest$HITId": "<p>The unique identifier of the HIT to retrieve review results for.</p>",
312        "ListReviewPolicyResultsForHITResponse$HITId": "<p>The HITId of the HIT for which results have been returned.</p>",
313        "ListReviewableHITsRequest$HITTypeId": "<p> The ID of the HIT type of the HITs to consider for the query. If not specified, all HITs for the Reviewer are considered </p>",
314        "ListWorkersWithQualificationTypeRequest$QualificationTypeId": "<p>The ID of the Qualification type of the Qualifications to return.</p>",
315        "Qualification$QualificationTypeId": "<p> The ID of the Qualification type for the Qualification.</p>",
316        "QualificationRequest$QualificationTypeId": "<p> The ID of the Qualification type the Worker is requesting, as returned by the CreateQualificationType operation. </p>",
317        "QualificationType$QualificationTypeId": "<p> A unique identifier for the Qualification type. A Qualification type is given a Qualification type ID when you call the CreateQualificationType operation. </p>",
318        "RejectAssignmentRequest$AssignmentId": "<p> The ID of the assignment. The assignment must correspond to a HIT created by the Requester. </p>",
319        "ReviewActionDetail$ActionId": "<p>The unique identifier for the action.</p>",
320        "ReviewActionDetail$TargetId": "<p> The specific HITId or AssignmentID targeted by the action.</p>",
321        "ReviewResultDetail$ActionId": "<p> A unique identifier of the Review action result. </p>",
322        "ReviewResultDetail$SubjectId": "<p>The HITID or AssignmentId about which this result was taken. Note that HIT-level Review Policies will often emit results about both the HIT itself and its Assignments, while Assignment-level review policies generally only emit results about the Assignment itself. </p>",
323        "ReviewResultDetail$QuestionId": "<p> Specifies the QuestionId the result is describing. Depending on whether the TargetType is a HIT or Assignment this results could specify multiple values. If TargetType is HIT and QuestionId is absent, then the result describes results of the HIT, including the HIT agreement score. If ObjectType is Assignment and QuestionId is absent, then the result describes the Worker's performance on the HIT. </p>",
324        "SendBonusRequest$AssignmentId": "<p>The ID of the assignment for which this bonus is paid.</p>",
325        "UpdateExpirationForHITRequest$HITId": "<p> The HIT to update. </p>",
326        "UpdateHITReviewStatusRequest$HITId": "<p> The ID of the HIT to update. </p>",
327        "UpdateHITTypeOfHITRequest$HITId": "<p>The HIT to update.</p>",
328        "UpdateHITTypeOfHITRequest$HITTypeId": "<p>The ID of the new HIT type.</p>",
329        "UpdateNotificationSettingsRequest$HITTypeId": "<p> The ID of the HIT type whose notification specification is being updated. </p>",
330        "UpdateQualificationTypeRequest$QualificationTypeId": "<p>The ID of the Qualification type to update.</p>"
331      }
332    },
333    "EventType": {
334      "base": null,
335      "refs": {
336        "EventTypeList$member": null,
337        "SendTestEventNotificationRequest$TestEventType": "<p> The event to simulate to test the notification specification. This event is included in the test message even if the notification specification does not include the event type. The notification specification does not filter out the test event. </p>"
338      }
339    },
340    "EventTypeList": {
341      "base": null,
342      "refs": {
343        "NotificationSpecification$EventTypes": "<p> The list of events that should cause notifications to be sent. Valid Values: AssignmentAccepted | AssignmentAbandoned | AssignmentReturned | AssignmentSubmitted | AssignmentRejected | AssignmentApproved | HITCreated | HITExtended | HITDisposed | HITReviewable | HITExpired | Ping. The Ping event is only valid for the SendTestEventNotification operation. </p>"
344      }
345    },
346    "ExceptionMessage": {
347      "base": null,
348      "refs": {
349        "RequestError$Message": null,
350        "ServiceFault$Message": null
351      }
352    },
353    "GetAccountBalanceRequest": {
354      "base": null,
355      "refs": {
356      }
357    },
358    "GetAccountBalanceResponse": {
359      "base": null,
360      "refs": {
361      }
362    },
363    "GetAssignmentRequest": {
364      "base": null,
365      "refs": {
366      }
367    },
368    "GetAssignmentResponse": {
369      "base": null,
370      "refs": {
371      }
372    },
373    "GetFileUploadURLRequest": {
374      "base": null,
375      "refs": {
376      }
377    },
378    "GetFileUploadURLResponse": {
379      "base": null,
380      "refs": {
381      }
382    },
383    "GetHITRequest": {
384      "base": null,
385      "refs": {
386      }
387    },
388    "GetHITResponse": {
389      "base": null,
390      "refs": {
391      }
392    },
393    "GetQualificationScoreRequest": {
394      "base": null,
395      "refs": {
396      }
397    },
398    "GetQualificationScoreResponse": {
399      "base": null,
400      "refs": {
401      }
402    },
403    "GetQualificationTypeRequest": {
404      "base": null,
405      "refs": {
406      }
407    },
408    "GetQualificationTypeResponse": {
409      "base": null,
410      "refs": {
411      }
412    },
413    "HIT": {
414      "base": "<p> The HIT data structure represents a single HIT, including all the information necessary for a Worker to accept and complete the HIT.</p>",
415      "refs": {
416        "CreateHITResponse$HIT": "<p> Contains the newly created HIT data. For a description of the HIT data structure as it appears in responses, see the HIT Data Structure documentation. </p>",
417        "CreateHITWithHITTypeResponse$HIT": "<p> Contains the newly created HIT data. For a description of the HIT data structure as it appears in responses, see the HIT Data Structure documentation. </p>",
418        "GetAssignmentResponse$HIT": "<p> The HIT associated with this assignment. The response includes one HIT element.</p>",
419        "GetHITResponse$HIT": "<p> Contains the requested HIT data.</p>",
420        "HITList$member": null
421      }
422    },
423    "HITAccessActions": {
424      "base": null,
425      "refs": {
426        "QualificationRequirement$ActionsGuarded": "<p> Setting this attribute prevents Workers whose Qualifications do not meet this QualificationRequirement from taking the specified action. Valid arguments include \"Accept\" (Worker cannot accept the HIT, but can preview the HIT and see it in their search results), \"PreviewAndAccept\" (Worker cannot accept or preview the HIT, but can see the HIT in their search results), and \"DiscoverPreviewAndAccept\" (Worker cannot accept, preview, or see the HIT in their search results). It's possible for you to create a HIT with multiple QualificationRequirements (which can have different values for the ActionGuarded attribute). In this case, the Worker is only permitted to perform an action when they have met all QualificationRequirements guarding the action. The actions in the order of least restrictive to most restrictive are Discover, Preview and Accept. For example, if a Worker meets all QualificationRequirements that are set to DiscoverPreviewAndAccept, but do not meet all requirements that are set with PreviewAndAccept, then the Worker will be able to Discover, i.e. see the HIT in their search result, but will not be able to Preview or Accept the HIT. ActionsGuarded should not be used in combination with the <code>RequiredToPreview</code> field. </p>"
427      }
428    },
429    "HITLayoutParameter": {
430      "base": "<p> The HITLayoutParameter data structure defines parameter values used with a HITLayout. A HITLayout is a reusable Amazon Mechanical Turk project template used to provide Human Intelligence Task (HIT) question data for CreateHIT. </p>",
431      "refs": {
432        "HITLayoutParameterList$member": null
433      }
434    },
435    "HITLayoutParameterList": {
436      "base": null,
437      "refs": {
438        "CreateHITRequest$HITLayoutParameters": "<p> If the HITLayoutId is provided, any placeholder values must be filled in with values using the HITLayoutParameter structure. For more information, see HITLayout. </p>",
439        "CreateHITWithHITTypeRequest$HITLayoutParameters": "<p> If the HITLayoutId is provided, any placeholder values must be filled in with values using the HITLayoutParameter structure. For more information, see HITLayout. </p>"
440      }
441    },
442    "HITList": {
443      "base": null,
444      "refs": {
445        "ListHITsForQualificationTypeResponse$HITs": "<p> The list of HIT elements returned by the query.</p>",
446        "ListHITsResponse$HITs": "<p> The list of HIT elements returned by the query.</p>",
447        "ListReviewableHITsResponse$HITs": "<p> The list of HIT elements returned by the query.</p>"
448      }
449    },
450    "HITReviewStatus": {
451      "base": null,
452      "refs": {
453        "HIT$HITReviewStatus": "<p> Indicates the review status of the HIT. Valid Values are NotReviewed | MarkedForReview | ReviewedAppropriate | ReviewedInappropriate.</p>"
454      }
455    },
456    "HITStatus": {
457      "base": null,
458      "refs": {
459        "HIT$HITStatus": "<p>The status of the HIT and its assignments. Valid Values are Assignable | Unassignable | Reviewable | Reviewing | Disposed. </p>"
460      }
461    },
462    "IdempotencyToken": {
463      "base": null,
464      "refs": {
465        "CreateAdditionalAssignmentsForHITRequest$UniqueRequestToken": "<p> A unique identifier for this request, which allows you to retry the call on error without extending the HIT multiple times. This is useful in cases such as network timeouts where it is unclear whether or not the call succeeded on the server. If the extend HIT already exists in the system from a previous call using the same <code>UniqueRequestToken</code>, subsequent calls will return an error with a message containing the request ID. </p>",
466        "CreateHITRequest$UniqueRequestToken": "<p> A unique identifier for this request which allows you to retry the call on error without creating duplicate HITs. This is useful in cases such as network timeouts where it is unclear whether or not the call succeeded on the server. If the HIT already exists in the system from a previous call using the same UniqueRequestToken, subsequent calls will return a AWS.MechanicalTurk.HitAlreadyExists error with a message containing the HITId. </p> <note> <p> Note: It is your responsibility to ensure uniqueness of the token. The unique token expires after 24 hours. Subsequent calls using the same UniqueRequestToken made after the 24 hour limit could create duplicate HITs. </p> </note>",
467        "CreateHITWithHITTypeRequest$UniqueRequestToken": "<p> A unique identifier for this request which allows you to retry the call on error without creating duplicate HITs. This is useful in cases such as network timeouts where it is unclear whether or not the call succeeded on the server. If the HIT already exists in the system from a previous call using the same UniqueRequestToken, subsequent calls will return a AWS.MechanicalTurk.HitAlreadyExists error with a message containing the HITId. </p> <note> <p> Note: It is your responsibility to ensure uniqueness of the token. The unique token expires after 24 hours. Subsequent calls using the same UniqueRequestToken made after the 24 hour limit could create duplicate HITs. </p> </note>",
468        "SendBonusRequest$UniqueRequestToken": "<p>A unique identifier for this request, which allows you to retry the call on error without granting multiple bonuses. This is useful in cases such as network timeouts where it is unclear whether or not the call succeeded on the server. If the bonus already exists in the system from a previous call using the same UniqueRequestToken, subsequent calls will return an error with a message containing the request ID.</p>"
469      }
470    },
471    "Integer": {
472      "base": null,
473      "refs": {
474        "AcceptQualificationRequestRequest$IntegerValue": "<p> The value of the Qualification. You can omit this value if you are using the presence or absence of the Qualification as the basis for a HIT requirement. </p>",
475        "AssociateQualificationWithWorkerRequest$IntegerValue": "<p>The value of the Qualification to assign.</p>",
476        "CreateAdditionalAssignmentsForHITRequest$NumberOfAdditionalAssignments": "<p>The number of additional assignments to request for this HIT.</p>",
477        "CreateHITRequest$MaxAssignments": "<p> The number of times the HIT can be accepted and completed before the HIT becomes unavailable. </p>",
478        "CreateHITWithHITTypeRequest$MaxAssignments": "<p> The number of times the HIT can be accepted and completed before the HIT becomes unavailable. </p>",
479        "CreateQualificationTypeRequest$AutoGrantedValue": "<p>The Qualification value to use for automatically granted Qualifications. This parameter is used only if the AutoGranted parameter is true.</p>",
480        "HIT$MaxAssignments": "<p>The number of times the HIT can be accepted and completed before the HIT becomes unavailable. </p>",
481        "HIT$NumberOfAssignmentsPending": "<p> The number of assignments for this HIT that are being previewed or have been accepted by Workers, but have not yet been submitted, returned, or abandoned.</p>",
482        "HIT$NumberOfAssignmentsAvailable": "<p> The number of assignments for this HIT that are available for Workers to accept.</p>",
483        "HIT$NumberOfAssignmentsCompleted": "<p> The number of assignments for this HIT that have been approved or rejected.</p>",
484        "IntegerList$member": null,
485        "ListAssignmentsForHITResponse$NumResults": "<p> The number of assignments on the page in the filtered results list, equivalent to the number of assignments returned by this call.</p>",
486        "ListBonusPaymentsResponse$NumResults": "<p>The number of bonus payments on this page in the filtered results list, equivalent to the number of bonus payments being returned by this call. </p>",
487        "ListHITsForQualificationTypeResponse$NumResults": "<p> The number of HITs on this page in the filtered results list, equivalent to the number of HITs being returned by this call. </p>",
488        "ListHITsResponse$NumResults": "<p>The number of HITs on this page in the filtered results list, equivalent to the number of HITs being returned by this call.</p>",
489        "ListQualificationRequestsResponse$NumResults": "<p>The number of Qualification requests on this page in the filtered results list, equivalent to the number of Qualification requests being returned by this call.</p>",
490        "ListQualificationTypesResponse$NumResults": "<p> The number of Qualification types on this page in the filtered results list, equivalent to the number of types this operation returns. </p>",
491        "ListReviewableHITsResponse$NumResults": "<p> The number of HITs on this page in the filtered results list, equivalent to the number of HITs being returned by this call. </p>",
492        "ListWorkerBlocksResponse$NumResults": "<p> The number of assignments on the page in the filtered results list, equivalent to the number of assignments returned by this call.</p>",
493        "ListWorkersWithQualificationTypeResponse$NumResults": "<p> The number of Qualifications on this page in the filtered results list, equivalent to the number of Qualifications being returned by this call.</p>",
494        "Qualification$IntegerValue": "<p> The value (score) of the Qualification, if the Qualification has an integer value.</p>",
495        "QualificationType$AutoGrantedValue": "<p> The Qualification integer value to use for automatically granted Qualifications, if AutoGranted is true. This is 1 by default. </p>",
496        "UpdateQualificationTypeRequest$AutoGrantedValue": "<p>The Qualification value to use for automatically granted Qualifications. This parameter is used only if the AutoGranted parameter is true.</p>"
497      }
498    },
499    "IntegerList": {
500      "base": null,
501      "refs": {
502        "QualificationRequirement$IntegerValues": "<p> The integer value to compare against the Qualification's value. IntegerValue must not be present if Comparator is Exists or DoesNotExist. IntegerValue can only be used if the Qualification type has an integer value; it cannot be used with the Worker_Locale QualificationType ID. When performing a set comparison by using the In or the NotIn comparator, you can use up to 15 IntegerValue elements in a QualificationRequirement data structure. </p>"
503      }
504    },
505    "ListAssignmentsForHITRequest": {
506      "base": null,
507      "refs": {
508      }
509    },
510    "ListAssignmentsForHITResponse": {
511      "base": null,
512      "refs": {
513      }
514    },
515    "ListBonusPaymentsRequest": {
516      "base": null,
517      "refs": {
518      }
519    },
520    "ListBonusPaymentsResponse": {
521      "base": null,
522      "refs": {
523      }
524    },
525    "ListHITsForQualificationTypeRequest": {
526      "base": null,
527      "refs": {
528      }
529    },
530    "ListHITsForQualificationTypeResponse": {
531      "base": null,
532      "refs": {
533      }
534    },
535    "ListHITsRequest": {
536      "base": null,
537      "refs": {
538      }
539    },
540    "ListHITsResponse": {
541      "base": null,
542      "refs": {
543      }
544    },
545    "ListQualificationRequestsRequest": {
546      "base": null,
547      "refs": {
548      }
549    },
550    "ListQualificationRequestsResponse": {
551      "base": null,
552      "refs": {
553      }
554    },
555    "ListQualificationTypesRequest": {
556      "base": null,
557      "refs": {
558      }
559    },
560    "ListQualificationTypesResponse": {
561      "base": null,
562      "refs": {
563      }
564    },
565    "ListReviewPolicyResultsForHITRequest": {
566      "base": null,
567      "refs": {
568      }
569    },
570    "ListReviewPolicyResultsForHITResponse": {
571      "base": null,
572      "refs": {
573      }
574    },
575    "ListReviewableHITsRequest": {
576      "base": null,
577      "refs": {
578      }
579    },
580    "ListReviewableHITsResponse": {
581      "base": null,
582      "refs": {
583      }
584    },
585    "ListWorkerBlocksRequest": {
586      "base": null,
587      "refs": {
588      }
589    },
590    "ListWorkerBlocksResponse": {
591      "base": null,
592      "refs": {
593      }
594    },
595    "ListWorkersWithQualificationTypeRequest": {
596      "base": null,
597      "refs": {
598      }
599    },
600    "ListWorkersWithQualificationTypeResponse": {
601      "base": null,
602      "refs": {
603      }
604    },
605    "Locale": {
606      "base": "<p>The Locale data structure represents a geographical region or location.</p>",
607      "refs": {
608        "LocaleList$member": null,
609        "Qualification$LocaleValue": null
610      }
611    },
612    "LocaleList": {
613      "base": null,
614      "refs": {
615        "QualificationRequirement$LocaleValues": "<p> The locale value to compare against the Qualification's value. The local value must be a valid ISO 3166 country code or supports ISO 3166-2 subdivisions. LocaleValue can only be used with a Worker_Locale QualificationType ID. LocaleValue can only be used with the EqualTo, NotEqualTo, In, and NotIn comparators. You must only use a single LocaleValue element when using the EqualTo or NotEqualTo comparators. When performing a set comparison by using the In or the NotIn comparator, you can use up to 30 LocaleValue elements in a QualificationRequirement data structure. </p>"
616      }
617    },
618    "Long": {
619      "base": null,
620      "refs": {
621        "CreateHITRequest$AutoApprovalDelayInSeconds": "<p> The number of seconds after an assignment for the HIT has been submitted, after which the assignment is considered Approved automatically unless the Requester explicitly rejects it. </p>",
622        "CreateHITRequest$LifetimeInSeconds": "<p> An amount of time, in seconds, after which the HIT is no longer available for users to accept. After the lifetime of the HIT elapses, the HIT no longer appears in HIT searches, even if not all of the assignments for the HIT have been accepted. </p>",
623        "CreateHITRequest$AssignmentDurationInSeconds": "<p> The amount of time, in seconds, that a Worker has to complete the HIT after accepting it. If a Worker does not complete the assignment within the specified duration, the assignment is considered abandoned. If the HIT is still active (that is, its lifetime has not elapsed), the assignment becomes available for other users to find and accept. </p>",
624        "CreateHITTypeRequest$AutoApprovalDelayInSeconds": "<p> The number of seconds after an assignment for the HIT has been submitted, after which the assignment is considered Approved automatically unless the Requester explicitly rejects it. </p>",
625        "CreateHITTypeRequest$AssignmentDurationInSeconds": "<p> The amount of time, in seconds, that a Worker has to complete the HIT after accepting it. If a Worker does not complete the assignment within the specified duration, the assignment is considered abandoned. If the HIT is still active (that is, its lifetime has not elapsed), the assignment becomes available for other users to find and accept. </p>",
626        "CreateHITWithHITTypeRequest$LifetimeInSeconds": "<p> An amount of time, in seconds, after which the HIT is no longer available for users to accept. After the lifetime of the HIT elapses, the HIT no longer appears in HIT searches, even if not all of the assignments for the HIT have been accepted. </p>",
627        "CreateQualificationTypeRequest$RetryDelayInSeconds": "<p>The number of seconds that a Worker must wait after requesting a Qualification of the Qualification type before the worker can retry the Qualification request.</p> <p>Constraints: None. If not specified, retries are disabled and Workers can request a Qualification of this type only once, even if the Worker has not been granted the Qualification. It is not possible to disable retries for a Qualification type after it has been created with retries enabled. If you want to disable retries, you must delete existing retry-enabled Qualification type and then create a new Qualification type with retries disabled.</p>",
628        "CreateQualificationTypeRequest$TestDurationInSeconds": "<p>The number of seconds the Worker has to complete the Qualification test, starting from the time the Worker requests the Qualification.</p>",
629        "HIT$AutoApprovalDelayInSeconds": "<p>The amount of time, in seconds, after the Worker submits an assignment for the HIT that the results are automatically approved by Amazon Mechanical Turk. This is the amount of time the Requester has to reject an assignment submitted by a Worker before the assignment is auto-approved and the Worker is paid. </p>",
630        "HIT$AssignmentDurationInSeconds": "<p> The length of time, in seconds, that a Worker has to complete the HIT after accepting it.</p>",
631        "QualificationType$TestDurationInSeconds": "<p> The amount of time, in seconds, given to a Worker to complete the Qualification test, beginning from the time the Worker requests the Qualification. </p>",
632        "QualificationType$RetryDelayInSeconds": "<p> The amount of time, in seconds, Workers must wait after taking the Qualification test before they can take it again. Workers can take a Qualification test multiple times if they were not granted the Qualification from a previous attempt, or if the test offers a gradient score and they want a better score. If not specified, retries are disabled and Workers can request a Qualification only once. </p>",
633        "UpdateQualificationTypeRequest$TestDurationInSeconds": "<p>The number of seconds the Worker has to complete the Qualification test, starting from the time the Worker requests the Qualification.</p>",
634        "UpdateQualificationTypeRequest$RetryDelayInSeconds": "<p>The amount of time, in seconds, that Workers must wait after requesting a Qualification of the specified Qualification type before they can retry the Qualification request. It is not possible to disable retries for a Qualification type after it has been created with retries enabled. If you want to disable retries, you must dispose of the existing retry-enabled Qualification type using DisposeQualificationType and then create a new Qualification type with retries disabled using CreateQualificationType.</p>"
635      }
636    },
637    "NotificationSpecification": {
638      "base": "<p>The NotificationSpecification data structure describes a HIT event notification for a HIT type.</p>",
639      "refs": {
640        "SendTestEventNotificationRequest$Notification": "<p> The notification specification to test. This value is identical to the value you would provide to the UpdateNotificationSettings operation when you establish the notification specification for a HIT type. </p>",
641        "UpdateNotificationSettingsRequest$Notification": "<p> The notification specification for the HIT type. </p>"
642      }
643    },
644    "NotificationTransport": {
645      "base": null,
646      "refs": {
647        "NotificationSpecification$Transport": "<p> The method Amazon Mechanical Turk uses to send the notification. Valid Values: Email | SQS | SNS. </p>"
648      }
649    },
650    "NotifyWorkersFailureCode": {
651      "base": null,
652      "refs": {
653        "NotifyWorkersFailureStatus$NotifyWorkersFailureCode": "<p> Encoded value for the failure type. </p>"
654      }
655    },
656    "NotifyWorkersFailureStatus": {
657      "base": "<p> When MTurk encounters an issue with notifying the Workers you specified, it returns back this object with failure details. </p>",
658      "refs": {
659        "NotifyWorkersFailureStatusList$member": null
660      }
661    },
662    "NotifyWorkersFailureStatusList": {
663      "base": null,
664      "refs": {
665        "NotifyWorkersResponse$NotifyWorkersFailureStatuses": "<p> When MTurk sends notifications to the list of Workers, it returns back any failures it encounters in this list of NotifyWorkersFailureStatus objects. </p>"
666      }
667    },
668    "NotifyWorkersRequest": {
669      "base": null,
670      "refs": {
671      }
672    },
673    "NotifyWorkersResponse": {
674      "base": null,
675      "refs": {
676      }
677    },
678    "PaginationToken": {
679      "base": "<p>If the previous response was incomplete (because there is more data to retrieve), Amazon Mechanical Turk returns a pagination token in the response. You can use this pagination token to retrieve the next set of results. </p>",
680      "refs": {
681        "ListAssignmentsForHITRequest$NextToken": "<p>Pagination token</p>",
682        "ListAssignmentsForHITResponse$NextToken": null,
683        "ListBonusPaymentsRequest$NextToken": "<p>Pagination token</p>",
684        "ListBonusPaymentsResponse$NextToken": null,
685        "ListHITsForQualificationTypeRequest$NextToken": "<p>Pagination Token</p>",
686        "ListHITsForQualificationTypeResponse$NextToken": null,
687        "ListHITsRequest$NextToken": "<p>Pagination token</p>",
688        "ListHITsResponse$NextToken": null,
689        "ListQualificationRequestsRequest$NextToken": null,
690        "ListQualificationRequestsResponse$NextToken": null,
691        "ListQualificationTypesRequest$NextToken": null,
692        "ListQualificationTypesResponse$NextToken": null,
693        "ListReviewPolicyResultsForHITRequest$NextToken": "<p>Pagination token</p>",
694        "ListReviewPolicyResultsForHITResponse$NextToken": null,
695        "ListReviewableHITsRequest$NextToken": "<p>Pagination Token</p>",
696        "ListReviewableHITsResponse$NextToken": null,
697        "ListWorkerBlocksRequest$NextToken": "<p>Pagination token</p>",
698        "ListWorkerBlocksResponse$NextToken": null,
699        "ListWorkersWithQualificationTypeRequest$NextToken": "<p>Pagination Token</p>",
700        "ListWorkersWithQualificationTypeResponse$NextToken": null
701      }
702    },
703    "ParameterMapEntry": {
704      "base": "<p> This data structure is the data type for the AnswerKey parameter of the ScoreMyKnownAnswers/2011-09-01 Review Policy. </p>",
705      "refs": {
706        "ParameterMapEntryList$member": null
707      }
708    },
709    "ParameterMapEntryList": {
710      "base": null,
711      "refs": {
712        "PolicyParameter$MapEntries": "<p> List of ParameterMapEntry objects. </p>"
713      }
714    },
715    "PolicyParameter": {
716      "base": "<p> Name of the parameter from the Review policy. </p>",
717      "refs": {
718        "PolicyParameterList$member": null
719      }
720    },
721    "PolicyParameterList": {
722      "base": null,
723      "refs": {
724        "ReviewPolicy$Parameters": "<p>Name of the parameter from the Review policy.</p>"
725      }
726    },
727    "Qualification": {
728      "base": "<p>The Qualification data structure represents a Qualification assigned to a user, including the Qualification type and the value (score).</p>",
729      "refs": {
730        "GetQualificationScoreResponse$Qualification": "<p> The Qualification data structure of the Qualification assigned to a user, including the Qualification type and the value (score). </p>",
731        "QualificationList$member": null
732      }
733    },
734    "QualificationList": {
735      "base": null,
736      "refs": {
737        "ListWorkersWithQualificationTypeResponse$Qualifications": "<p> The list of Qualification elements returned by this call. </p>"
738      }
739    },
740    "QualificationRequest": {
741      "base": "<p> The QualificationRequest data structure represents a request a Worker has made for a Qualification. </p>",
742      "refs": {
743        "QualificationRequestList$member": null
744      }
745    },
746    "QualificationRequestList": {
747      "base": null,
748      "refs": {
749        "ListQualificationRequestsResponse$QualificationRequests": "<p>The Qualification request. The response includes one QualificationRequest element for each Qualification request returned by the query.</p>"
750      }
751    },
752    "QualificationRequirement": {
753      "base": "<p> The QualificationRequirement data structure describes a Qualification that a Worker must have before the Worker is allowed to accept a HIT. A requirement may optionally state that a Worker must have the Qualification in order to preview the HIT, or see the HIT in search results. </p>",
754      "refs": {
755        "QualificationRequirementList$member": null
756      }
757    },
758    "QualificationRequirementList": {
759      "base": null,
760      "refs": {
761        "CreateHITRequest$QualificationRequirements": "<p> Conditions that a Worker's Qualifications must meet in order to accept the HIT. A HIT can have between zero and ten Qualification requirements. All requirements must be met in order for a Worker to accept the HIT. Additionally, other actions can be restricted using the <code>ActionsGuarded</code> field on each <code>QualificationRequirement</code> structure. </p>",
762        "CreateHITTypeRequest$QualificationRequirements": "<p> Conditions that a Worker's Qualifications must meet in order to accept the HIT. A HIT can have between zero and ten Qualification requirements. All requirements must be met in order for a Worker to accept the HIT. Additionally, other actions can be restricted using the <code>ActionsGuarded</code> field on each <code>QualificationRequirement</code> structure. </p>",
763        "HIT$QualificationRequirements": "<p> Conditions that a Worker's Qualifications must meet in order to accept the HIT. A HIT can have between zero and ten Qualification requirements. All requirements must be met in order for a Worker to accept the HIT. Additionally, other actions can be restricted using the <code>ActionsGuarded</code> field on each <code>QualificationRequirement</code> structure. </p>"
764      }
765    },
766    "QualificationStatus": {
767      "base": null,
768      "refs": {
769        "ListWorkersWithQualificationTypeRequest$Status": "<p> The status of the Qualifications to return. Can be <code>Granted | Revoked</code>. </p>",
770        "Qualification$Status": "<p> The status of the Qualification. Valid values are Granted | Revoked.</p>"
771      }
772    },
773    "QualificationType": {
774      "base": "<p> The QualificationType data structure represents a Qualification type, a description of a property of a Worker that must match the requirements of a HIT for the Worker to be able to accept the HIT. The type also describes how a Worker can obtain a Qualification of that type, such as through a Qualification test. </p>",
775      "refs": {
776        "CreateQualificationTypeResponse$QualificationType": "<p>The created Qualification type, returned as a QualificationType data structure.</p>",
777        "GetQualificationTypeResponse$QualificationType": "<p> The returned Qualification Type</p>",
778        "QualificationTypeList$member": null,
779        "UpdateQualificationTypeResponse$QualificationType": "<p> Contains a QualificationType data structure.</p>"
780      }
781    },
782    "QualificationTypeList": {
783      "base": null,
784      "refs": {
785        "ListQualificationTypesResponse$QualificationTypes": "<p> The list of QualificationType elements returned by the query. </p>"
786      }
787    },
788    "QualificationTypeStatus": {
789      "base": null,
790      "refs": {
791        "CreateQualificationTypeRequest$QualificationTypeStatus": "<p>The initial status of the Qualification type.</p> <p>Constraints: Valid values are: Active | Inactive</p>",
792        "QualificationType$QualificationTypeStatus": "<p> The status of the Qualification type. A Qualification type's status determines if users can apply to receive a Qualification of this type, and if HITs can be created with requirements based on this type. Valid values are Active | Inactive. </p>",
793        "UpdateQualificationTypeRequest$QualificationTypeStatus": "<p>The new status of the Qualification type - Active | Inactive</p>"
794      }
795    },
796    "RejectAssignmentRequest": {
797      "base": null,
798      "refs": {
799      }
800    },
801    "RejectAssignmentResponse": {
802      "base": null,
803      "refs": {
804      }
805    },
806    "RejectQualificationRequestRequest": {
807      "base": null,
808      "refs": {
809      }
810    },
811    "RejectQualificationRequestResponse": {
812      "base": null,
813      "refs": {
814      }
815    },
816    "RequestError": {
817      "base": "<p>Your request is invalid.</p>",
818      "refs": {
819      }
820    },
821    "ResultSize": {
822      "base": null,
823      "refs": {
824        "ListAssignmentsForHITRequest$MaxResults": null,
825        "ListBonusPaymentsRequest$MaxResults": null,
826        "ListHITsForQualificationTypeRequest$MaxResults": "<p> Limit the number of results returned. </p>",
827        "ListHITsRequest$MaxResults": null,
828        "ListQualificationRequestsRequest$MaxResults": "<p> The maximum number of results to return in a single call. </p>",
829        "ListQualificationTypesRequest$MaxResults": "<p> The maximum number of results to return in a single call. </p>",
830        "ListReviewPolicyResultsForHITRequest$MaxResults": "<p>Limit the number of results returned.</p>",
831        "ListReviewableHITsRequest$MaxResults": "<p> Limit the number of results returned. </p>",
832        "ListWorkerBlocksRequest$MaxResults": null,
833        "ListWorkersWithQualificationTypeRequest$MaxResults": "<p> Limit the number of results returned. </p>"
834      }
835    },
836    "ReviewActionDetail": {
837      "base": "<p> Both the AssignmentReviewReport and the HITReviewReport elements contains the ReviewActionDetail data structure. This structure is returned multiple times for each action specified in the Review Policy. </p>",
838      "refs": {
839        "ReviewActionDetailList$member": null
840      }
841    },
842    "ReviewActionDetailList": {
843      "base": null,
844      "refs": {
845        "ReviewReport$ReviewActions": "<p> A list of ReviewAction objects for each action specified in the Review Policy. </p>"
846      }
847    },
848    "ReviewActionStatus": {
849      "base": null,
850      "refs": {
851        "ReviewActionDetail$Status": "<p> The current disposition of the action: INTENDED, SUCCEEDED, FAILED, or CANCELLED. </p>"
852      }
853    },
854    "ReviewPolicy": {
855      "base": "<p> HIT Review Policy data structures represent HIT review policies, which you specify when you create a HIT. </p>",
856      "refs": {
857        "CreateHITRequest$AssignmentReviewPolicy": "<p> The Assignment-level Review Policy applies to the assignments under the HIT. You can specify for Mechanical Turk to take various actions based on the policy. </p>",
858        "CreateHITRequest$HITReviewPolicy": "<p> The HIT-level Review Policy applies to the HIT. You can specify for Mechanical Turk to take various actions based on the policy. </p>",
859        "CreateHITWithHITTypeRequest$AssignmentReviewPolicy": "<p> The Assignment-level Review Policy applies to the assignments under the HIT. You can specify for Mechanical Turk to take various actions based on the policy. </p>",
860        "CreateHITWithHITTypeRequest$HITReviewPolicy": "<p> The HIT-level Review Policy applies to the HIT. You can specify for Mechanical Turk to take various actions based on the policy. </p>",
861        "ListReviewPolicyResultsForHITResponse$AssignmentReviewPolicy": "<p> The name of the Assignment-level Review Policy. This contains only the PolicyName element. </p>",
862        "ListReviewPolicyResultsForHITResponse$HITReviewPolicy": "<p>The name of the HIT-level Review Policy. This contains only the PolicyName element.</p>"
863      }
864    },
865    "ReviewPolicyLevel": {
866      "base": null,
867      "refs": {
868        "ReviewPolicyLevelList$member": null
869      }
870    },
871    "ReviewPolicyLevelList": {
872      "base": null,
873      "refs": {
874        "ListReviewPolicyResultsForHITRequest$PolicyLevels": "<p> The Policy Level(s) to retrieve review results for - HIT or Assignment. If omitted, the default behavior is to retrieve all data for both policy levels. For a list of all the described policies, see Review Policies. </p>"
875      }
876    },
877    "ReviewReport": {
878      "base": "<p> Contains both ReviewResult and ReviewAction elements for a particular HIT. </p>",
879      "refs": {
880        "ListReviewPolicyResultsForHITResponse$AssignmentReviewReport": "<p> Contains both ReviewResult and ReviewAction elements for an Assignment. </p>",
881        "ListReviewPolicyResultsForHITResponse$HITReviewReport": "<p>Contains both ReviewResult and ReviewAction elements for a particular HIT. </p>"
882      }
883    },
884    "ReviewResultDetail": {
885      "base": "<p> This data structure is returned multiple times for each result specified in the Review Policy. </p>",
886      "refs": {
887        "ReviewResultDetailList$member": null
888      }
889    },
890    "ReviewResultDetailList": {
891      "base": null,
892      "refs": {
893        "ReviewReport$ReviewResults": "<p> A list of ReviewResults objects for each action specified in the Review Policy. </p>"
894      }
895    },
896    "ReviewableHITStatus": {
897      "base": null,
898      "refs": {
899        "ListReviewableHITsRequest$Status": "<p> Can be either <code>Reviewable</code> or <code>Reviewing</code>. Reviewable is the default value. </p>"
900      }
901    },
902    "SendBonusRequest": {
903      "base": null,
904      "refs": {
905      }
906    },
907    "SendBonusResponse": {
908      "base": null,
909      "refs": {
910      }
911    },
912    "SendTestEventNotificationRequest": {
913      "base": null,
914      "refs": {
915      }
916    },
917    "SendTestEventNotificationResponse": {
918      "base": null,
919      "refs": {
920      }
921    },
922    "ServiceFault": {
923      "base": "<p>Amazon Mechanical Turk is temporarily unable to process your request. Try your call again.</p>",
924      "refs": {
925      }
926    },
927    "String": {
928      "base": null,
929      "refs": {
930        "AcceptQualificationRequestRequest$QualificationRequestId": "<p>The ID of the Qualification request, as returned by the <code>GetQualificationRequests</code> operation.</p>",
931        "ApproveAssignmentRequest$RequesterFeedback": "<p> A message for the Worker, which the Worker can see in the Status section of the web site. </p>",
932        "Assignment$Answer": "<p> The Worker's answers submitted for the HIT contained in a QuestionFormAnswers document, if the Worker provides an answer. If the Worker does not provide any answers, Answer may contain a QuestionFormAnswers document, or Answer may be empty.</p>",
933        "Assignment$RequesterFeedback": "<p> The feedback string included with the call to the ApproveAssignment operation or the RejectAssignment operation, if the Requester approved or rejected the assignment and specified feedback.</p>",
934        "BonusPayment$Reason": "<p>The Reason text given when the bonus was granted, if any.</p>",
935        "CreateHITRequest$Title": "<p> The title of the HIT. A title should be short and descriptive about the kind of task the HIT contains. On the Amazon Mechanical Turk web site, the HIT title appears in search results, and everywhere the HIT is mentioned. </p>",
936        "CreateHITRequest$Keywords": "<p> One or more words or phrases that describe the HIT, separated by commas. These words are used in searches to find HITs. </p>",
937        "CreateHITRequest$Description": "<p> A general description of the HIT. A description includes detailed information about the kind of task the HIT contains. On the Amazon Mechanical Turk web site, the HIT description appears in the expanded view of search results, and in the HIT and assignment screens. A good description gives the user enough information to evaluate the HIT before accepting it. </p>",
938        "CreateHITRequest$Question": "<p> The data the person completing the HIT uses to produce the results. </p> <p> Constraints: Must be a QuestionForm data structure, an ExternalQuestion data structure, or an HTMLQuestion data structure. The XML question data must not be larger than 64 kilobytes (65,535 bytes) in size, including whitespace. </p> <p>Either a Question parameter or a HITLayoutId parameter must be provided.</p>",
939        "CreateHITRequest$RequesterAnnotation": "<p> An arbitrary data field. The RequesterAnnotation parameter lets your application attach arbitrary data to the HIT for tracking purposes. For example, this parameter could be an identifier internal to the Requester's application that corresponds with the HIT. </p> <p> The RequesterAnnotation parameter for a HIT is only visible to the Requester who created the HIT. It is not shown to the Worker, or any other Requester. </p> <p> The RequesterAnnotation parameter may be different for each HIT you submit. It does not affect how your HITs are grouped. </p>",
940        "CreateHITTypeRequest$Title": "<p> The title of the HIT. A title should be short and descriptive about the kind of task the HIT contains. On the Amazon Mechanical Turk web site, the HIT title appears in search results, and everywhere the HIT is mentioned. </p>",
941        "CreateHITTypeRequest$Keywords": "<p> One or more words or phrases that describe the HIT, separated by commas. These words are used in searches to find HITs. </p>",
942        "CreateHITTypeRequest$Description": "<p> A general description of the HIT. A description includes detailed information about the kind of task the HIT contains. On the Amazon Mechanical Turk web site, the HIT description appears in the expanded view of search results, and in the HIT and assignment screens. A good description gives the user enough information to evaluate the HIT before accepting it. </p>",
943        "CreateHITWithHITTypeRequest$Question": "<p> The data the person completing the HIT uses to produce the results. </p> <p> Constraints: Must be a QuestionForm data structure, an ExternalQuestion data structure, or an HTMLQuestion data structure. The XML question data must not be larger than 64 kilobytes (65,535 bytes) in size, including whitespace. </p> <p>Either a Question parameter or a HITLayoutId parameter must be provided.</p>",
944        "CreateHITWithHITTypeRequest$RequesterAnnotation": "<p> An arbitrary data field. The RequesterAnnotation parameter lets your application attach arbitrary data to the HIT for tracking purposes. For example, this parameter could be an identifier internal to the Requester's application that corresponds with the HIT. </p> <p> The RequesterAnnotation parameter for a HIT is only visible to the Requester who created the HIT. It is not shown to the Worker, or any other Requester. </p> <p> The RequesterAnnotation parameter may be different for each HIT you submit. It does not affect how your HITs are grouped. </p>",
945        "CreateQualificationTypeRequest$Name": "<p> The name you give to the Qualification type. The type name is used to represent the Qualification to Workers, and to find the type using a Qualification type search. It must be unique across all of your Qualification types.</p>",
946        "CreateQualificationTypeRequest$Keywords": "<p>One or more words or phrases that describe the Qualification type, separated by commas. The keywords of a type make the type easier to find during a search.</p>",
947        "CreateQualificationTypeRequest$Description": "<p>A long description for the Qualification type. On the Amazon Mechanical Turk website, the long description is displayed when a Worker examines a Qualification type.</p>",
948        "CreateQualificationTypeRequest$Test": "<p> The questions for the Qualification test a Worker must answer correctly to obtain a Qualification of this type. If this parameter is specified, <code>TestDurationInSeconds</code> must also be specified. </p> <p>Constraints: Must not be longer than 65535 bytes. Must be a QuestionForm data structure. This parameter cannot be specified if AutoGranted is true.</p> <p>Constraints: None. If not specified, the Worker may request the Qualification without answering any questions.</p>",
949        "CreateQualificationTypeRequest$AnswerKey": "<p>The answers to the Qualification test specified in the Test parameter, in the form of an AnswerKey data structure.</p> <p>Constraints: Must not be longer than 65535 bytes.</p> <p>Constraints: None. If not specified, you must process Qualification requests manually.</p>",
950        "CreateWorkerBlockRequest$Reason": "<p>A message explaining the reason for blocking the Worker. This parameter enables you to keep track of your Workers. The Worker does not see this message.</p>",
951        "DeleteWorkerBlockRequest$Reason": "<p>A message that explains the reason for unblocking the Worker. The Worker does not see this message.</p>",
952        "DisassociateQualificationFromWorkerRequest$Reason": "<p>A text message that explains why the Qualification was revoked. The user who had the Qualification sees this message.</p>",
953        "GetFileUploadURLRequest$QuestionIdentifier": "<p>The identifier of the question with a FileUploadAnswer, as specified in the QuestionForm of the HIT.</p>",
954        "GetFileUploadURLResponse$FileUploadURL": "<p> A temporary URL for the file that the Worker uploaded for the answer. </p>",
955        "HIT$Title": "<p> The title of the HIT.</p>",
956        "HIT$Description": "<p> A general description of the HIT.</p>",
957        "HIT$Question": "<p> The data the Worker completing the HIT uses produce the results. This is either either a QuestionForm, HTMLQuestion or an ExternalQuestion data structure.</p>",
958        "HIT$Keywords": "<p> One or more words or phrases that describe the HIT, separated by commas. Search terms similar to the keywords of a HIT are more likely to have the HIT in the search results.</p>",
959        "HIT$RequesterAnnotation": "<p> An arbitrary data field the Requester who created the HIT can use. This field is visible only to the creator of the HIT.</p>",
960        "HITLayoutParameter$Name": "<p> The name of the parameter in the HITLayout. </p>",
961        "HITLayoutParameter$Value": "<p>The value substituted for the parameter referenced in the HITLayout. </p>",
962        "ListQualificationTypesRequest$Query": "<p> A text query against all of the searchable attributes of Qualification types. </p>",
963        "NotificationSpecification$Destination": "<p> The target for notification messages. The Destination’s format is determined by the specified Transport: </p> <ul> <li> <p>When Transport is Email, the Destination is your email address.</p> </li> <li> <p>When Transport is SQS, the Destination is your queue URL.</p> </li> <li> <p>When Transport is SNS, the Destination is the ARN of your topic.</p> </li> </ul>",
964        "NotificationSpecification$Version": "<p>The version of the Notification API to use. Valid value is 2006-05-05.</p>",
965        "NotifyWorkersFailureStatus$NotifyWorkersFailureMessage": "<p> A message detailing the reason the Worker could not be notified. </p>",
966        "NotifyWorkersRequest$Subject": "<p>The subject line of the email message to send. Can include up to 200 characters.</p>",
967        "NotifyWorkersRequest$MessageText": "<p>The text of the email message to send. Can include up to 4,096 characters</p>",
968        "ParameterMapEntry$Key": "<p> The QuestionID from the HIT that is used to identify which question requires Mechanical Turk to score as part of the ScoreMyKnownAnswers/2011-09-01 Review Policy. </p>",
969        "PolicyParameter$Key": "<p> Name of the parameter from the list of Review Polices. </p>",
970        "QualificationRequest$QualificationRequestId": "<p>The ID of the Qualification request, a unique identifier generated when the request was submitted. </p>",
971        "QualificationRequest$Test": "<p> The contents of the Qualification test that was presented to the Worker, if the type has a test and the Worker has submitted answers. This value is identical to the QuestionForm associated with the Qualification type at the time the Worker requests the Qualification.</p>",
972        "QualificationRequest$Answer": "<p> The Worker's answers for the Qualification type's test contained in a QuestionFormAnswers document, if the type has a test and the Worker has submitted answers. If the Worker does not provide any answers, Answer may be empty. </p>",
973        "QualificationRequirement$QualificationTypeId": "<p> The ID of the Qualification type for the requirement.</p>",
974        "QualificationType$Name": "<p> The name of the Qualification type. The type name is used to identify the type, and to find the type using a Qualification type search. </p>",
975        "QualificationType$Description": "<p> A long description for the Qualification type. </p>",
976        "QualificationType$Keywords": "<p> One or more words or phrases that describe theQualification type, separated by commas. The Keywords make the type easier to find using a search. </p>",
977        "QualificationType$Test": "<p> The questions for a Qualification test associated with this Qualification type that a user can take to obtain a Qualification of this type. This parameter must be specified if AnswerKey is present. A Qualification type cannot have both a specified Test parameter and an AutoGranted value of true. </p>",
978        "QualificationType$AnswerKey": "<p>The answers to the Qualification test specified in the Test parameter.</p>",
979        "RejectAssignmentRequest$RequesterFeedback": "<p> A message for the Worker, which the Worker can see in the Status section of the web site. </p>",
980        "RejectQualificationRequestRequest$QualificationRequestId": "<p> The ID of the Qualification request, as returned by the <code>ListQualificationRequests</code> operation. </p>",
981        "RejectQualificationRequestRequest$Reason": "<p>A text message explaining why the request was rejected, to be shown to the Worker who made the request.</p>",
982        "ReviewActionDetail$ActionName": "<p> The nature of the action itself. The Review Policy is responsible for examining the HIT and Assignments, emitting results, and deciding which other actions will be necessary. </p>",
983        "ReviewActionDetail$TargetType": "<p> The type of object in TargetId.</p>",
984        "ReviewActionDetail$Result": "<p> A description of the outcome of the review.</p>",
985        "ReviewActionDetail$ErrorCode": "<p> Present only when the Results have a FAILED Status.</p>",
986        "ReviewPolicy$PolicyName": "<p> Name of a Review Policy: SimplePlurality/2011-09-01 or ScoreMyKnownAnswers/2011-09-01 </p>",
987        "ReviewResultDetail$SubjectType": "<p> The type of the object from the SubjectId field.</p>",
988        "ReviewResultDetail$Key": "<p> Key identifies the particular piece of reviewed information. </p>",
989        "ReviewResultDetail$Value": "<p> The values of Key provided by the review policies you have selected. </p>",
990        "SendBonusRequest$Reason": "<p>A message that explains the reason for the bonus payment. The Worker receiving the bonus can see this message.</p>",
991        "StringList$member": null,
992        "UpdateQualificationTypeRequest$Description": "<p>The new description of the Qualification type.</p>",
993        "UpdateQualificationTypeRequest$Test": "<p>The questions for the Qualification test a Worker must answer correctly to obtain a Qualification of this type. If this parameter is specified, <code>TestDurationInSeconds</code> must also be specified.</p> <p>Constraints: Must not be longer than 65535 bytes. Must be a QuestionForm data structure. This parameter cannot be specified if AutoGranted is true.</p> <p>Constraints: None. If not specified, the Worker may request the Qualification without answering any questions.</p>",
994        "UpdateQualificationTypeRequest$AnswerKey": "<p>The answers to the Qualification test specified in the Test parameter, in the form of an AnswerKey data structure.</p>",
995        "WorkerBlock$Reason": "<p> A message explaining the reason the Worker was blocked. </p>"
996      }
997    },
998    "StringList": {
999      "base": null,
1000      "refs": {
1001        "ParameterMapEntry$Values": "<p> The list of answers to the question specified in the MapEntry Key element. The Worker must match all values in order for the answer to be scored correctly. </p>",
1002        "PolicyParameter$Values": "<p> The list of values of the Parameter</p>"
1003      }
1004    },
1005    "Timestamp": {
1006      "base": null,
1007      "refs": {
1008        "Assignment$AutoApprovalTime": "<p> If results have been submitted, AutoApprovalTime is the date and time the results of the assignment results are considered Approved automatically if they have not already been explicitly approved or rejected by the Requester. This value is derived from the auto-approval delay specified by the Requester in the HIT. This value is omitted from the assignment if the Worker has not yet submitted results.</p>",
1009        "Assignment$AcceptTime": "<p> The date and time the Worker accepted the assignment.</p>",
1010        "Assignment$SubmitTime": "<p> If the Worker has submitted results, SubmitTime is the date and time the assignment was submitted. This value is omitted from the assignment if the Worker has not yet submitted results.</p>",
1011        "Assignment$ApprovalTime": "<p> If the Worker has submitted results and the Requester has approved the results, ApprovalTime is the date and time the Requester approved the results. This value is omitted from the assignment if the Requester has not yet approved the results.</p>",
1012        "Assignment$RejectionTime": "<p> If the Worker has submitted results and the Requester has rejected the results, RejectionTime is the date and time the Requester rejected the results.</p>",
1013        "Assignment$Deadline": "<p> The date and time of the deadline for the assignment. This value is derived from the deadline specification for the HIT and the date and time the Worker accepted the HIT.</p>",
1014        "BonusPayment$GrantTime": "<p>The date and time of when the bonus was granted.</p>",
1015        "HIT$CreationTime": "<p> The date and time the HIT was created.</p>",
1016        "HIT$Expiration": "<p>The date and time the HIT expires.</p>",
1017        "Qualification$GrantTime": "<p> The date and time the Qualification was granted to the Worker. If the Worker's Qualification was revoked, and then re-granted based on a new Qualification request, GrantTime is the date and time of the last call to the AcceptQualificationRequest operation.</p>",
1018        "QualificationRequest$SubmitTime": "<p>The date and time the Qualification request had a status of Submitted. This is either the time the Worker submitted answers for a Qualification test, or the time the Worker requested the Qualification if the Qualification type does not have a test. </p>",
1019        "QualificationType$CreationTime": "<p> The date and time the Qualification type was created. </p>",
1020        "ReviewActionDetail$CompleteTime": "<p> The date when the action was completed.</p>",
1021        "UpdateExpirationForHITRequest$ExpireAt": "<p> The date and time at which you want the HIT to expire </p>"
1022      }
1023    },
1024    "TurkErrorCode": {
1025      "base": null,
1026      "refs": {
1027        "RequestError$TurkErrorCode": null,
1028        "ServiceFault$TurkErrorCode": null
1029      }
1030    },
1031    "UpdateExpirationForHITRequest": {
1032      "base": null,
1033      "refs": {
1034      }
1035    },
1036    "UpdateExpirationForHITResponse": {
1037      "base": null,
1038      "refs": {
1039      }
1040    },
1041    "UpdateHITReviewStatusRequest": {
1042      "base": null,
1043      "refs": {
1044      }
1045    },
1046    "UpdateHITReviewStatusResponse": {
1047      "base": null,
1048      "refs": {
1049      }
1050    },
1051    "UpdateHITTypeOfHITRequest": {
1052      "base": null,
1053      "refs": {
1054      }
1055    },
1056    "UpdateHITTypeOfHITResponse": {
1057      "base": null,
1058      "refs": {
1059      }
1060    },
1061    "UpdateNotificationSettingsRequest": {
1062      "base": null,
1063      "refs": {
1064      }
1065    },
1066    "UpdateNotificationSettingsResponse": {
1067      "base": null,
1068      "refs": {
1069      }
1070    },
1071    "UpdateQualificationTypeRequest": {
1072      "base": null,
1073      "refs": {
1074      }
1075    },
1076    "UpdateQualificationTypeResponse": {
1077      "base": null,
1078      "refs": {
1079      }
1080    },
1081    "WorkerBlock": {
1082      "base": "<p> The WorkerBlock data structure represents a Worker who has been blocked. It has two elements: the WorkerId and the Reason for the block. </p>",
1083      "refs": {
1084        "WorkerBlockList$member": null
1085      }
1086    },
1087    "WorkerBlockList": {
1088      "base": null,
1089      "refs": {
1090        "ListWorkerBlocksResponse$WorkerBlocks": "<p> The list of WorkerBlocks, containing the collection of Worker IDs and reasons for blocking.</p>"
1091      }
1092    }
1093  }
1094}
1095