Error Code | Description |
90001 | JSON format parsing failed. Check whether the request packet conforms to the JSON Specification. |
90005 | The JSON format request body lacks the MsgRandom field or the MsgRandom field is not of Integer type. |
90009 | The request requires App administrator permissions. |
90018 | Number of requested accounts exceeds the limit. |
90020 | The tag length exceeds the limit (must not exceed 50 bytes). |
90022 | Duplicate tags exist in the TagsOr and TagsAnd push conditions. |
90024 | Excessive frequency of push. The push interval must be greater than 1 second. |
90026 | Error in offline message storage time. |
90032 | The number of tags in the push condition exceeds 10, or the number of tags in the add tag request exceeds 10. |
90033 | Invalid attribute. |
90039 | Push by attribute and Tag Push cannot coexist. |
90040 | One of the push conditions has an empty tag. |
90045 | Push notification feature for all users/Tag/single push is not enabled. |
90047 | Push times exceed the daily limit (default: 100). |
90049 | Invalid TaskId returned, no push record. Push via the all users/Tag Push or single push API, and the TaskId returned can be used for withdrawal. |
90050 | Repeated withdrawal. Push tasks that have already been withdrawn cannot be called repeatedly. |
90051 | Withdrawal too frequent, withdrawal frequency limit is 1/s. |
90052 | The withdrawal validity period has expired. Withdrawal must be requested within 24 hours. Push tasks exceeding 24 hours cannot be withdrawn. |
90053 | Withdrawal unavailable. The push task is designated not stored on the roaming server/unread (OnlineOnlyFlag = 0), but OfflinePushInfo was not carried along during withdrawal. |
90056 | The request body for All Users Push is too large. Currently supports a maximum length of 10K. |
91000 | Internal Server Error, please retry. |
Error Code | Description |
800001 | Register push service. The appKey parameter is invalid. |
800002 | Register push service. The sdkAppId parameter is invalid. |
800003 | Initialize SDK failed. |
800004 | Long link establishment failed. |
800005 | Push failure on local machine channel. |
800006 | Push failure on local machine channel, attempt FCM channel registration failed. |
800007 | Failed to detect ALL channels. |
800008 | Push service registration timeout. |
800009 | Push token is empty. |
800010 | Set token for SDK failed. |
800011 | Failed to disable automatic sign-up. |
800012 | Failed to disable push permission request. |
800013 | Failed to create notification channel. |
800014 | Failed to set push configuration. |
800015 | Experimental API call failure. |
800016 | User refused push pop-up permission. |
6014 | IM account not logged in, please log in first to register for push services. |
9523 | Please check whether the network is functioning properly. |
70016 | PublicKey does not exist. UserSig verification failed. Please confirm whether the correct appKey is used. |
Error Code | Description |
-1 | Unknown error. |
0 | Success. |
1 | Internal error. |
10001 | System error. |
10002 | System busy. |
10003 | Remote service error. |
10008 | Parameter error, refer to the API document. |
10012 | Invalid request. |
10016 | Missing required parameter. |
10017 | Invalid parameter value. |
10027 | API calls are too frequent. |
10029 | Illegal device. When initiating app-related operations, such as register or unregister, the corresponding device cannot be found. |
10030 | The app retrieves invalid regid too frequently. |
10031 | The app is in the blocklist. Message sending is prohibited. |
10032 | The app retrieves invalid alias too frequently. |
10033 | The app is in the blocklist. feedback requests are forbidden. |
10034 | The app's message count exceeds the limit for the current day. |
10035 | No more invalid aliases are available for retrieval. |
10036 | Application operations are forbidden. |
10037 | Request expired. |
10038 | Application access to statistics and trace data is forbidden. |
10039 | The app retrieves message statistics and trace data too frequently. |
20607 | DB error. |
20209 | Invalid topic. |
20215 | Subscription topic failed. |
20216 | Failed to unsubscribe from the topic. |
20301 | Failed to send message. |
20315 | Failed to delete broadcast message. |
21301 | Authentication failed. |
21302 | token authentication failed. |
21303 | Restricted request. |
21305 | Missing necessary parameter. |
22000 | Illegal application. |
22006 | Invalid APP ID. |
22007 | Invalid application Key. |
22022 | Invalid application package name. |
22102 | Failed to send application notification message. |
26003 | Message Push internal invocation failed. |
26004 | Broadcast Message sent too frequently. |
26005 | account settings are too frequent and forbidden. |
26006 | Send for review. Please review promptly. |
27001 | channel information mismatch. |
65003 | Device not found, usually due to the device being offline. |
65006 | Alias settings are too frequent and forbidden. |
65007 | Alias is in the blocklist. |
65008 | Alias exceeds the length limit. |
65009 | Message content is too long. |
65010 | Topic exceeds the length limit. |
65011 | Parameter not provided. |
65012 | Alias is empty. |
65013 | Topic is empty. |
65014 | Too many key-value pairs. |
65015 | The total length of key-value pairs is too long. |
65016 | User account is empty. |
65017 | User account is too long. |
65028 | No message found. |
65029 | Remote service exception. |
65030 | An exception occurred while building JSON. |
65035 | Too many topics. |
65036 | Callback parameter is too long. |
65037 | Callback URL is too long. |
65038 | Invalid Callback URL. |
65040 | Cancellation failed. |
65041 | ImeiMd5 is empty. |
65042 | Invalid ImeiMd5. |
66006 | Registration failed. This refers to an exception in Android device registration, including device registration and application registration. |
66007 | Invalid regId, indicating the regId format is incorrect. |
66008 | Invalid request. |
66108 | Invalid parameter information sent. |
66109 | Invalid regSecret. |
66300 | Unknown command. |
66301 | Command execution error. |
66303 | Xiaomi ID is empty. |
66304 | Xiaomi ID is too long. |
66305 | Invalid Xiaomi ID. Xiaomi ID format is incorrect. |
66306 | Failed to toggle push on or off. |
66307 | The message ID passed in to delete scheduled task job is invalid. |
66308 | Scoring service request parameters are illegal. |
70011 | Input is empty. |
70012 | Invalid JobKey format. |
200001 | The number of pushes exceeds the daily limit. |
200002 | Push QPS exceeds the limit. |
Error Code | Description |
-5 | Get Token. Task failed. |
502 | Connection request exception, often due to unstable network condition. |
503 | Traffic control. |
6003 | Fingerprint certificate configuration inconsistency. |
6004 | API authentication failed: permission not found. |
80100003 | Message structure error. |
80100016 | The message body contains sensitive words. |
80300002 | Deliver message to specified user (Token): permission denied. |
80300007 | Specified Token is invalid. |
907122036 | Push notification rights and interests are not enabled. |
907122046 | Push service unavailable. |
907122047 | Common error code. |
907122054 | Push SDK is initializing automatically. Please retry later. |
907122069 | Sub-user operation is not supported. |
907135000 | Invalid passed parameters. |
907135003 | SDK failed to connect to HMS Core (APK). |
907135700 | Invoke gateway to query app scope failed. |
907135701 |
Error Code | Description |
-2 | Server traffic control. |
-1 | The service is unavailable. Developers, please try again later. |
0 | Success indicates the API call is successful. |
11 | Invalid AuthToken. |
12 | Incorrect HTTP method. |
13 | Application call count exceeds limit, including call frequency exceeds limit. |
14 | Invalid AppKey parameter. |
15 | AppKey parameter is missing. |
16 | Signature verification failed, invalid signature. |
17 | Missing signature parameter. |
18 | Timestamp parameter is missing. |
19 | Invalid timestamp parameter. |
20 | Non-existing method name. |
21 | Missing method name parameter. |
22 | Version parameter is missing. |
23 | Illegal version parameter, user-submitted version number has invalid format, must be numeric format. |
24 | Unsupported version number, user-submitted version number is not provided. |
25 | Encoding error, this normally occurs when the user does not use UTF-8 encoding in the HTTP request. |
26 | IP blocklist. |
27 | No permission for this feature. Access denied. |
28 | Application unavailable. |
29 | Auth Token parameter is missing. |
30 | This application has no permission for API push. |
31 | data not exist |
32 | Data duplication. |
33 | Message count exceeds the daily limit. |
34 | Image upload exceeds the daily limit. |
40 | Missing required parameters. Parameters marked as required in the API document must be passed. Please carefully check the document. |
41 | Parameter error, usually caused by illegal user input parameters. Please check carefully whether the input parameter format and range have a one-to-one correspondence. |
51 | The image is invalid, usually due to image format, resolution, or size not meeting requirements, or the image being unuploaded. Please check the image format and file upload method carefully. |
55 | Application access frequency limit. |
59 | No permission for link jump. Access denied. |
67 | Classification error (includes strong reminder for all exceptions). |
Error Code | Description |
0 | Request succeeded. |
10000 | Authentication failed. |
10006 | Alias length exceeds 70 characters. |
10043 | The push channel of this application is closed. |
10045 | Official messages cannot be sent during application review. |
10050 | alias and regId cannot both be empty. |
10051 | classification does not support this message type. |
10054 | Invalid notifyType. |
10055 | title cannot be empty. |
10056 | title length cannot exceed 40 characters. |
10057 | content cannot be empty. |
10058 | content length cannot exceed 100 characters. |
10059 | timeToLive is invalid. |
10060 | Invalid skipType. |
10061 | skipType = 2, skipContent cannot be empty. |
10062 | skipType = 2, skipContent must not exceed 2048 characters. |
10063 | skipType = 3, skipContent cannot be empty. |
10064 | skipType = 3, skipContent must not exceed 2048 characters. |
10065 | Invalid networkType. |
10067 | Invalid custom key and value key-value pair. |
10068 | skipType = 4, skipContent cannot be empty. |
10069 | skipType = 4, skipContent must not exceed 2048 characters. |
10070 | Message-sending volume exceeds the total amount limit. |
10071 | The send time exceeds the allowed range. |
10072 | Push speed is too fast, try again later. |
10073 | System message-sending volume exceeds the total amount limit. |
10082 | System message toggle is not on. |
10092 | The profileId length exceeds the limit. |
10094 | The authentication code and the AppID in the request body do not match. |
10095 | Invalid notifyId. |
10096 | category error. |
10097 | category does not match classification. |
10103 | Push content contains sensitive information. |
10104 | Send an official message. |
10150 | aliases and regIds cannot both be empty. |
10151 | taskId cannot be empty. |
10152 | taskId is invalid. |
10153 | regIds count is not within specified range [2-1000]. |
10154 | aliases count is not within specified range [2-1000]. |
10155 | The message does not exist or has expired. |
10200 | The AppID cannot be empty. |
10201 | The appKey cannot be empty. |
10202 | Invalid appKey. |
10203 | The timestamp cannot be empty. |
10204 | The sign cannot be empty. |
10205 | The AppID does not exist. |
10206 | The sign is incorrect. |
10207 | The timestamp is invalid. |
10252 | The batch message body exceeds the limit. |
10255 | The full push interface is not yet open. |
10301 | alias length cannot exceed 70 characters |
10302 | Invalid regId. |
10304 | extra contains an unsupported key. |
10305 | extra callback length exceeds the limit. |
10306 | extra callback.param length exceeds the limit. |
10307 | alias is invalid. |
10311 | The device is currently unable to push. |
10352 | The requestId cannot be empty. |
10353 | requestId length cannot exceed 64 characters. |
10471 | The number of taskIds cannot exceed 100. |
10472 | taskIds format is invalid. |
10473 | taskIds is empty. |
10600 | The name parameter is invalid. |
10601 | The tag name cannot be empty. |
10602 | The tag description cannot exceed 300 characters. |
10603 | The oldName parameter cannot be empty. |
10604 | The newName parameter cannot be empty. |
10605 | The oldName parameter is invalid. |
10606 | The newName parameter is invalid. |
10608 | The type parameter cannot be empty. |
10609 | The ids parameter cannot be empty. |
10610 | Tag name already exists. |
10611 | Category name already exists. |
10612 | Tag combination name already exists. |
10613 | The group parameter is invalid. |
10614 | The number of ids cannot exceed 1000. |
10615 | The number of tags cannot exceed 100. |
10616 | The type parameter is invalid. |
10700 | The userids cannot be empty. |
10701 | The UserID count exceeds the limit. |
10703 | exceed the upper limit, try again later. |
10704 | requestId length cannot exceed 64 characters. |
10706 | userType error. |
10800 | registration_tokens count is not within specified range. |
10801 | The notification cannot be empty. |
10802 | The original_source_name cannot be empty. |
10803 | The original_source_name length is illegal. |
10804 | The original_source_ip cannot be empty. |
10806 | Invalid click_action. |
10807 | The url length exceeds the limit. |
10808 | The intent length exceeds the limit. |
Error Code | Description |
200 | Normal. |
500 | Other exceptions. |
1001 | System error. |
1003 | Server busy. |
1005 | Parameter error, refer to the API document. |
1006 | Signature authentication failed. |
110000 | Invalid AppID. |
110001 | Invalid appKey. |
110004 | Parameter cannot be empty. |
110009 | The app is added to the blocklist. |
110010 | Push rate is too fast. |
110053 | The passthrough exceeds the limit. |
201 | No permission, server proactively denies. |
501 | Failed to push message (db_error). |
513 | Failed to push message. |
519 | Failed to push message due to service overload. |
520 | Message fold (received multiple times from the same application on the same device within 1 minute, default 5 times). |
110002 | Push ID invalid (Push ID not subscribed). |
110003 | Invalid pushId. |
110005 | Alias invalid (alias not subscribed or message switch is off). |
110010 | Invalid pushId (message switch is off). |
Error Code | Description |
200 | Success. |
400 | Parameter error. |
403 | Authentication failed. |
404 | Service not found. |
500 | Internal server error. |
502 | Connection request exception, often due to unstable network condition. |
503 | Frequent request, please retry. |
80100000 | Some tokens were sent successfully, and the returned failTokens are those that failed to send. |
80100003 | Message structure error. |
80300006 | Duplicate Token. |
80300007 | ALL Push Tokens are invalid. |
80300008 | The message body size exceeds the system setting default value (4096 Bytes). |
80300010 | The number of Push Tokens cannot exceed 1000 each time. |
80200020 | Receipt mismatch. |
10001 | The timestamp is empty. |
10207 | The timestamp is invalid. |
10300 | Token is empty. |
10205 | The appId is empty. |
Error Code | Description |
400 | INVALID_ARGUMENT, possible reasons including invalid registration, invalid package name, excessively large message, invalid data key, invalid TTL or other invalid parameters. |
404 | UNREGISTERED. The reason may be lack of registration token or the token is unregistered. |
403 | SENDER_ID_MISMATCH. A registration token is associated with a specific group of senders. When a client application registers with FCM, it must specify which senders have permission to send messages. When sending a message to a client application, you should use one of these sender IDs. If you switch to another sender, the existing registration token will not work. |
429 | QUOTA_EXCEEDED. This error might be caused by exceeding the message rate quota, device message rate quota, or topic message rate quota. |
503 | UNAVAILABLE. The server is unable to process the request in time. |
500 | INTERNAL: The server encountered an error while attempting to process the request. |
Error Code | Description |
200 | Success. |
403 | BadCertificate: The certificate is invalid. |
| BadCertificateEnvironment: The client certificate environment is invalid. |
| ExpiredProviderToken: The provider token is outdated. Generate a new token. |
| InvalidProviderToken: The provider token is invalid or unable to verify the token signature. |
410 | ExpiredToken: The device token has expired. |
Feedback