Error Codes

If an API fails to be called, an error code, instead of the service data, is returned. The returned error code can be used to identify the failure cause. In the HTTP protocol, a 4xx or 5xx response will be returned when an error occurs. The response contains the specific error code and information. If you are unable to identify the cause of an error, contact customer service and provide the error code so that we can help you solve the problem as soon as possible.

Error Response Body Format

If an error occurs during API calling, an error code and a message will be displayed. The following shows an error response body.

{
    "error_msg": "attached policies per agency limit exceeded",
    "error_code": "PAP5.0003",
    "request_id": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}

In the response body, error_code is an error code, error_msg provides information about the error, and request_id indicates the request ID.

In particular, if an error occurs due to lack of permissions, the error response body is as follows:

{
    "error_msg": "access denied: xxx...xxx",
    "error_code": "PAP5.0001",
    "request_id": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
    "encoded_authorization_message": "xxx...xxx"
}

In the response body, encoded_authorization_message is an additional field provided in this scenario, and indicates the encrypted authentication failure information. It can be decrypted using the STS5 decryption API.

Error Code Description

**Table 1** Error codes
Status Code	Error Code	Error Message	Description	Measure
400	PAP5.0010	invalid marker	Invalid marker.	Check the value of the marker field.
400	PAP5.0011	malformed policy document	Incorrect identity policy or trust policy.	Check the value of the policy document field.
400	PAP5.0029	invalid agency name	Invalid trust agency name.	Check the value of the agency name field.
400	PAP5.0030	invalid path	Invalid path.	Check the value of the path field.
400	PAP5.0033	duplicate key	Duplicate key value.	Check the request or contact technical support.
400	PAP5.0036	tag non-compliant	The tag value conflicts with preset tag policies.	Check the request or contact technical support.
400	PAP5.0038	This operation is only supported by v5 agencies	This operation is only supported by trust agencies.	Check the request or contact technical support.
400	PAP5.0040	invalid caller	Invalid caller.	Check whether the caller is the IAM user.
400	PAP5.0041	invalid serial number	Invalid serial number.	Check the value of the serial number field.
400	PAP5.0046	missing header `x-user-profile`	The x-user-profile is missing in the request header.	Check the request or contact technical support.
403	PAP5.0001	access denied: %s	Access denied.	Check whether this operation is allowed.
404	PAP5.0012	no such agency	Agency or trust agency not found.	Check the request or contact technical support.
404	PAP5.0014	no such authorization schema	Authorization summary not found.	Check the request or contact technical support.
404	PAP5.0015	no such deletion task	Deletion task not found.	Check the request or contact technical support.
404	PAP5.0016	no such group	User group not found.	Check the request or contact technical support.
404	PAP5.0018	no such policy	Identity policy not found.	Check the request or contact technical support.
404	PAP5.0019	no such policy attachment	Identity policy attachment record not found.	Check the request or contact technical support.
404	PAP5.0020	no such policy version	Identity policy version not found.	Check the request or contact technical support.
404	PAP5.0021	no such user	IAM user not found.	Check the request or contact technical support.
404	PAP5.0022	no such service linked agency	Service-linked agency not found.	Check the request or contact technical support.
404	PAP5.0023	no such service principal	Service principal not found.	Check the request or contact technical support.
404	PAP5.0034	no such domain	Tenant not found.	Check the request or contact technical support.
404	PAP5.0037	Resource tag not found	Resource tag not found.	Check the request or contact technical support.
409	PAP5.0003	attached policies per agency limit exceeded	Maximum identity policy attachments reached for a single agency or trust agency.	Detach unnecessary identity policies from the agency or trust agency.
409	PAP5.0004	attached policies per group limit exceeded	Maximum identity policy attachments reached for a user group.	Detach unnecessary identity policies from the user group.
409	PAP5.0005	attached policies per user limit exceeded	Maximum identity policy attachments reached for an IAM user.	Detach unnecessary identity policies from the IAM user.
409	PAP5.0006	concurrent modification	Concurrent modifications.	Try again later.
409	PAP5.0007	delete conflict: %s	Conflict exists and deletion failed.	Resolve the conflict.
409	PAP5.0024	policies limit exceeded	Maximum custom identity policies reached.	Delete unnecessary custom identity policies.
409	PAP5.0025	policy already exists	Identity policy already exists.	Check the request or contact technical support.
409	PAP5.0026	policy attachment already exists	Identity policy already attached.	Check the request or contact technical support.
409	PAP5.0027	policy size limit exceeded	Maximum number of bytes %d of an identity policy or trust policy reached (excluding blank characters).	Simplify the identity policy or trust policy.
409	PAP5.0028	versions per policy limit exceeded	Maximum versions reached for an identity policy.	Delete unnecessary identity policy versions.
409	PAP5.0031	agency already exists	The agency or trust agency already exists.	Check the request or contact technical support.
409	PAP5.0035	tags limit exceeded	Maximum tags reached.	Check the request or contact technical support.
409	PAP5.0039	mfa device already exists	The virtual MFA device already exists.	Check the request or contact technical support.
409	PAP5.0042	user already exists	The IAM user already exists.	Check the request or contact technical support.
409	PAP5.0043	group already exists	The user group already exists.	Check the request or contact technical support.
409	PAP5.0044	user already in group	The IAM user already exists in the user group.	Check the request.
409	PAP5.0045	login profile already exists	The login information already exists.	Check the request or contact technical support.