Common API call error codes-Phone Number Protection(PNP)-阿里云帮助中心

This topic lists common error codes for API calls. Use these error codes and their corresponding messages to troubleshoot issues.

Common API error codes

Error code	Error message	Suggested action
OK	The request was successful.	The request was successful.
isp.RAM_PERMISSION_DENY	RAM permission denied.	Grant the required permissions to the RAM user. For more information, see Identity management.
isv.OUT_OF_SERVICE	Service is suspended.	Check if your account has an overdue payment in the User Center and top up your account if necessary.
isv.PRODUCT_UN_SUBSCRIPT	Alibaba Cloud customers without active Cloud Communication products	Check if Alibaba Cloud Phone Number Protection is activated for the account associated with the current AccessKey.
isv.PRODUCT_UNSUBSCRIBE	Product not activated.	Verify that the Alibaba Cloud account for the current AccessKey has activated Phone Number Protection.
isv.ACCOUNT_NOT_EXISTS	The account does not exist.	Verify your account information.
isv.ACCOUNT_ABNORMAL	Abnormal account status.	Check if your account has an overdue payment, or try calling the API operation again later.
isp.SYSTEM_ERROR	System error.	Try calling the API operation again later.
isp.UNKNOWN_ERR_CODE	Unknown carrier error.	Try calling the API operation again later.
isv.PARTNER_NOT_EXIST	Unknown partner.	Try calling the API operation again later.
isv.NO_NOT_EXIST	The phone number does not exist.	Verify that the phone number belongs to your account.
isv.ILLEGAL_ARGUMENT	Invalid parameter.	Check that the input parameters meet the requirements.
isp.DAO_EXCEPTION	Database exception.	Try calling the API operation again later.
isv.NO_AVAILABLE_NUMBER	No available phone numbers.	Check the phone number binding rate. Also, verify that the number you are trying to attach does not already have a binding relationship with a number in the pool.
isv.FLOW_LIMIT	Throttling.	Ensure that you call the API operation within the throttling limits.
isv.FORBIDDEN_ACTION	Operation not permitted.	Check the returned message for more detailed error information. Common causes include the following: updateEndDate\|updateNoB\|updateNoA: The binding has expired. You must update the binding. confirmSend: The text message record has expired because it is more than one day old. createSubs: Phone number X does not exist or does not belong to this number pool. createAxgGroup: The number pool is not an AXG pool.
isv.EXPIRE_DATE_ILLEGAL	Invalid expiration time.	Check that the binding expiration time is in the correct format and is at least one minute later than the current system time.
isv.MOBILE_NUMBER_ILLEGAL	Invalid phone number format.	Check that the phone number format is correct. The phone number must contain only digits and no other characters, such as spaces.
isv.BIND_CONFLICT	Binding conflict.	Check if phone number A or phone number B already has a binding relationship with the private number X.
isv.SUBS_NOT_EXIST	The binding relationship does not exist.	Check if the binding relationship has expired. Also, verify that the number pool, private number, and binding relationship match.
isv.BUY_NUM_OVER_LIMIT	The number of purchased phone numbers exceeds the limit.	The number of phone numbers in a single purchase cannot exceed 10,000. Also, check that you have completed the required number of ID Verifications.
isv.POOLKEY_NOT_EXISTS	The number pool does not exist.	Check that the number pool key is correct.
isp.GATEWAY_ERROR	Failed to call the sending application module.	The sending application module failed to be called. Try sending the request again later.
isv.INVALID_PARAMETERS	Incorrect parameter format.	Check that the input parameters meet the requirements.
isv.UPDATE_CONFLICT	Update binding conflict.	Please verify that the updated A/B numbers are attached to this privacy number.
isp.FLOW_LIMITED	Throttling.	Ensure that you call the API operation within the throttling limits.
isv.EXCEED_LIMIT	The number of private numbers that can be attached exceeds the limit.	Phone number A and phone number B have reached the maximum number of bindings. You can change phone number A or B, or detach an existing binding.
isv.UNBIND_LOCK_FAILED	Failed to acquire a lock during detachment.	You can retry the operation or remove the 'pessimistic locking for detachment' tag from the number pool.
isv.PHONE_NOT_EXISTS	The phone number does not exist.	The phone number does not exist or has been released.
isv.PHONE_BIND_EXISTS	The phone number has a binding relationship.	The phone number cannot be released because it has an existing binding. You must detach the binding first.
isv.UPDATE_LOCK_FAILED	Failed to acquire a lock when updating the binding.	A lock could not be acquired on the private number. Try calling the API operation again later.
isv.PHONE_NOT_MATCH_POOLKEY	The phone number does not match the number pool.	Check the input parameters to confirm that the phone number belongs to the specified number pool.
isp.PARTNER_MODE_LIMITED	Incorrect number pool type.	Check that the number pool key is correct.

Other common error codes

Error code	Error message	Suggested action
0	Success.	The request message was processed successfully.
400	Invalid format.	The request message is in an invalid format. You must reassemble the message in the correct format and send the request again.
402	The phone number already has a binding relationship.	The virtual number requested for the binding has already been assigned to another user. You must request a different virtual number.
402	Insufficient number pool resources.	No available virtual numbers can be allocated. You can request new number resources or wait for an existing binding to be detached before you send the request again.
402	The specified phone number was not found.	The virtual number requested for the binding was not found in the number pool. You must use a correct virtual number and send the request again.
403	The binding relationship does not exist.	The binding relationship identity provided in the request does not exist in the 95 landline system. You must use a correct binding relationship identity and send the request again.