Data returned by the client V3 architecture - Captcha - Alibaba Cloud Documentation Center

In the client V3 architecture of Captcha 2.0, the Captcha service performs behavioral verification by checking whether the answer is correct and the request is from a machine. After the check, the service returns a verification code and other parameters to the client. You can use the Network feature in your browser to view the returned data.

Name			Type	Description
HTTP Status Code			Integer	The HTTP status code. For more information, see Return parameter descriptions.
HTTP Body	RequestId		String	The request ID.
	Success		Boolean	Indicates whether the request was successful. true: The request was successful. false: The request failed.
	Code		String	The return code. For more information, see Return parameter descriptions.
	Message		String	The detailed message. For more information, see Return parameter descriptions.
	Result	VerifyResult	Boolean	The verification result. true: The verification passed. false: The verification failed.
		VerifyCode	String	T001	The client verification passed.
				T005	Test mode is enabled in the console and configured to pass verification. If you have questions, log on to the Captcha 2.0 console to view the policy status configuration for the scenario. For more information, see Integration guide.
				T006	The request hit a whitelist policy and passed verification. If you have questions, log on to the Captcha 2.0 console to view the details of the whitelist policy.
				F001	A suspected attack request. The request failed the risk policy check. If you have questions, submit a ticket for troubleshooting.
				F004	Test mode is enabled in the console and configured to fail verification. If you have questions, log on to the Captcha 2.0 console to view the policy status configuration for the scenario. For more information, see Scenario management.
				F008	Duplicate submission of verification data. Each verification code request can be submitted only once.
				F009	A virtual device environment was detected. Check if you are using a virtual machine, such as VMware, VirtualBox, Hyper-V, or Parallels. Also check for emulators, such as AVD, BlueStacks, or VBox/Hyper-V, or a desktop browser that impersonates a mobile device. If you do not want to block these requests, log on to the Captcha 2.0 console and disable this check in the custom policy. For more information, see Set a custom policy.
				F010	The access frequency from the same IP address exceeded the limit. To configure a custom frequency threshold, log on to the Captcha 2.0 console and set a custom policy. For more information, see Set a custom policy.
				F011	The access frequency from the same device exceeded the limit. To configure a custom frequency threshold, log on to the Captcha 2.0 console and set a custom policy. For more information, see Set a custom policy.
				F014	No initialization record. This can happen for two reasons: The interval between the verification request and the initialization request exceeded 20 minutes. The backend deletes the initialization record. Send another initialization request and try again. The initialization record does not exist. This may be a suspected attack request or an integration error. Send a client initialization request before you send a verification request.
				F015	The verification interaction failed. For example, the puzzle piece was not moved to the correct position. Refresh the Captcha and complete the interaction again.
				F016	The request failed because of the URL verification policy configured in the console. Log on to the Captcha 2.0 console to adjust the URL verification policy in your custom policy. For more information, see Set a custom policy.
				F017	A suspected attack request. The request failed due to an abnormal protocol or parameter.

The following table describes the HTTP Status Code, Code, and Message parameters.

HTTP Status Code	Code	Message
200	Success	The operation was successful.
400	MissingParameter	A required parameter is missing.
401	InvalidParameter	The parameter is invalid.
403	Forbidden.AccountAccessDenied	You do not have permission. The service may not be activated, or your account may have an overdue payment.
403	Forbidden.RAMUserAccessDenied	The Resource Access Management (RAM) user does not have permission. Grant the AliyunYundunAFSFullAccess permission. For more information, see Grant permissions to a RAM role.
500	InternalError	An internal system error occurred. Retry the operation. If the error persists, submit a ticket and contact us.