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

During behavioral verification for the Captcha 2.0 client V3 architecture, the Captcha server verifies the user's response to determine if the request is from a bot. The server then returns a verification code and other parameters to your client. You can view this response data in the Network tab of your browser's developer tools.

Parameter			Type	Description
HTTP status code			Integer	The HTTP status code. For more information, see Return parameter descriptions.
HTTP body	Request ID		String	The request ID.
	Success		Boolean	Indicates whether the request was successful. true: The request was successful. false: The request failed.
	Code		String	The response code. For more information, see Return parameter descriptions.
	Message		String	Detailed information about the response. For more information, see Return parameter descriptions.
	Result	Verification result	Boolean	The verification result. true: The verification passed. false: The verification failed.
		Verification code	String	T001	Client-side verification passed.
				T002	The queries per second (QPS) throttling disaster recovery strategy was triggered. Captcha 2.0 supports a default of 1,000 QPS per tenant. If this threshold is exceeded, the service fails open, allowing requests to pass without security protection. If you need a higher business capacity, you can purchase additional QPS. The new quota does not take effect immediately. Contact your account manager to configure it at least two business days in advance.
				T005	Test mode is enabled in the console and configured to pass verification. Log on to the Captcha 2.0 Console to check the policy status for the relevant scenario. For detailed instructions, see Integration guide.
				T006	The request passed because it matched an allowlist policy. Log on to the Captcha 2.0 Console to view the configuration details of the allowlist policy.
				F001	A potential attack was detected, and the request was blocked by the risk control policy. For troubleshooting, submit a ticket.
				F004	Test mode is enabled in the console and configured to fail verification. Log on to the Captcha 2.0 Console to check the policy status for the relevant scenario. For detailed instructions, see Scenario management.
				F008	Duplicate verification data was submitted. Each verification request can be submitted only once.
				F009	The system detected a virtual device environment. Check if you are using a virtual machine, such as VMware, VirtualBox, Hyper-V, or Parallels; an emulator, such as AVD, BlueStacks, or VBox/Hyper-V; or a desktop browser emulating a mobile device. To allow these environments, log on to the Captcha 2.0 Console and disable this check in your custom policy settings. For detailed instructions, see Set up 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 modify your custom policy. For detailed instructions, see Set up 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 modify your custom policy. For detailed instructions, see Set up a custom policy.
				F014	No initialization record was found. This may occur for one of the following reasons: The interval between the initialization and verification requests exceeded 20 minutes, causing the backend to delete the initialization record. You must initiate a new request. The initialization record does not exist. This may indicate a potential attack or an integration error. You must initiate a client initialization request before sending a verification request.
				F015	The user failed the verification challenge. For example, the puzzle piece was not moved to the correct position. You can refresh the CAPTCHA and try again.
				F016	The request was blocked by the URL verification configured in a custom policy. To adjust this setting, log on to the Captcha 2.0 Console and modify the URL verification policy. For detailed instructions, see Set up a custom policy.
				F017	A potential attack was detected. The request failed due to an abnormal protocol or invalid parameters.
				F022	Verification failed in the V3 architecture's encryption mode. This can be caused by client-side resource abuse or incorrect client integration. For integration instructions, see V3 architecture encryption mode integration guide.
				F024	Automated script actions such as simulated clicks and swipes are detected. If you use tools like touch-emulator in a Vue application to simulate touch events on a desktop, or you have other legitimate simulated click scenarios, you can disable this check. To do so, disableIntercept Simulated Click Behavior inCustom Policy. For more information, see Set a custom policy.
				F025	The request was identified as abnormal by AI analysis based on the Qwen large language model. To disable this AI-powered security feature: Log on to the Captcha Console. Go to the Overview page, and click Expand Details on the product card in the upper-right corner. Click the AI-Powered Protection switch.

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

HTTP status code	Code	Message
200	Success	Success
400	MissingParameter	A required parameter is missing.
401	InvalidParameter	A parameter is invalid.
403	Forbidden.AccountAccessDenied	You do not have permission to perform this operation. This may be because the service is not activated or your account has an overdue payment.
403	Forbidden.RAMUserAccessDenied	The RAM user is not authorized to perform this operation. Grant the AliyunYundunAFSFullAccess permission to the RAM user. For detailed instructions, see Manage RAM role permissions.
500	InternalError	An internal server error occurred. We recommend that you try again. If the error persists, submit a ticket.