Messaging
SCG API Error codes
These are error codes and descriptions provided synchronously in API Responses.
|
HTTP Status |
Error Code |
Error Description |
More Info |
| 400 | SCG_ERROR_4001 |
Required parameter <parameter> missing or is null |
Retry after defining the missing parameter |
| 400 | SCG_ERROR_4002 | Required parameter <parameter> data type/format is incorrect | Retry after correcting the data type/format of the parameter |
| 400 | SCG_ERROR_4003 | Optional parameter <parameter> data type/format is incorrect | Retry after correcting the data type/format of the parameter |
| 400 | SCG_ERROR_4004 | Invalid parameter <parameter> defined | Retry after removing the invalid parameter |
| 400 | SCG_ERROR_4005 | Error message contains details about the limit being exceeded - Message size exceeds system limit | Retry after reducing the Message size |
| 400 | SCG_ERROR_4006 | Indexed parameter <parameter> too long - Value of <parameter> in the request exceeded the maximum allowed length | Retry after reducing the parameter length |
| 400 | SCG_ERROR_4007 |
Invalid Tracking URL - The tracking URL <parameter> that was provided is invalid |
Retry after changing the tracking URL |
| 400 | SCG_ERROR_4008 | Message scheduled time exceeds max allowed days: <parameter> | Retry after changing the max allowed days |
| 400 | SCG_ERROR_4009 |
Cannot exceed more than <parameter> media URLs |
Retry after changing the max allowed number |
| 400 | SCG_ERROR_40010 |
Cannot include media URLs with attachment |
Use the "media_urls" parameter or the "attachments" parameter. Retry after the correction |
|
400 |
SCG_ERROR_40011 |
Group message only supported for US Phone numbers |
Retry after correcting the data type/format of the parameter |
|
400 |
SCG_ERROR_40012 |
No sender addresses capable of sending requested message type |
Retry after reviewing request parameters |
|
400 |
SCG_ERROR_40013 |
No sender addresses capable of sending requested verifiedSms message |
Retry after reviewing request parameters |
|
400 |
SCG_ERROR_40014 |
Cannot failover to SMS on a message with attachments |
Retry after correcting the data type/format of the parameter |
|
400 |
SCG_ERROR_40015 |
Cannot exceed more than <parameter> recipients |
Retry after changing the max allowed recipients |
|
400 |
SCG_ERROR_40016 |
Sender id is not capable of sending MMS |
Retry after correcting the data type/format of the parameter |
|
400 |
SCG_ERROR_40017 |
Only sender id with type id LONGCODE is supported for group MMS |
Retry after correcting the data type/format of the parameter |
|
400 |
SCG_ERROR_40018 |
Invalid senderId/address: <parameter> |
Retry after correcting the data type/format of the parameter |
|
400 |
SCG_ERROR_40019 |
Multiple sender id with address: <parameter>. Use sender id to send message. |
Retry after correcting the data type/format of the parameter |
|
400 |
SCG_ERROR_40020 |
Unrecognized option(s): <parameter> |
Retry after correcting the data type/format of the parameter |
|
400 |
SCG_ERROR_40021 |
Failover to SMS requires a SenderId for SMS (use a channel) |
Retry after correcting the data type/format of the parameter |
|
400 |
SCG_ERROR_40022 |
Failover TO SMS requires a SenderId for <parameter> (use a channel) |
Retry after correcting the data type/format of the parameter |
|
400 |
SCG_ERROR_40023 |
Delivery Window Restriction Violation |
Retry after correcting the window |
|
400 |
SCG_ERROR_40024 |
Invalid Recipient |
Check to make sure you have the correct recipient address/format in your “to” address |
|
400 |
SCG_ERROR_40025 |
Invalid payload |
Please check whether you are sending the JSON and it is not empty |
| 400 | SCG_ERROR_40026 | Missing form-data part: <part> | Retry after correcting the required part |
| 400 | SCG_ERROR_40027 | Content size in Content-Disposition is mandatory | Retry after correcting the required content size |
| 400 | SCG_ERROR_40028 | Content length is mandatory | Retry after correcting the required content length |
| 400 | SCG_ERROR_40029 | Attachment size <parameter> exceeds max allowed attachment size <parameter> | Retry after reviewing parameters |
| 400 | SCG_ERROR_40030 | Only UPLOADED attachments can be downloaded. | Retry after reviewing parameters |
|
|
|
|
|
| 401 | SCG_ERROR_4010 |
Token unauthorized for this resource |
Retry after changing the authorized token |
|
|
|||
| 402 | SCG_ERROR_4020 |
Insufficient credit |
Please contact Syniverse support |
| 402 | SCG_ERROR_4021 | Quota exceeded | Please contact Syniverse support |
| 403 | SCG_ERROR_4030 | Forbidden | Please check the parameters you are trying to pass |
| 403 |
SCG_ERROR_4031 |
Attachment <parameter> was not found neither in cache nor in database |
Retry after reviewing request parameters |
|
403 |
SCG_ERROR_4032 |
Attachment <parameter> is in incorrect state <parameter> |
Please contact Syniverse support |
|
403 |
SCG_ERROR_4033 |
SenderId start date in the future: <parameter> |
Please contact Syniverse support |
|
403 |
SCG_ERROR_4034 |
SenderId end date in the past: <parameter> |
Please contact Syniverse support |
|
403 |
SCG_ERROR_4035 |
Invalid sender ID state: <parameter> |
Please contact Syniverse support |
|
403 |
SCG_ERROR_4036 |
Invalid sender ID ownership: <parameter> |
Please contact Syniverse support |
| 403 | SCG_ERROR_4037 | <parameter> forbidden for attachment in state: <parameter> | Please contact Syniverse support |
| 404 | SCG_ERROR_4040 |
Resource you are trying to fetch not found for <parameter(s)> |
Retry after reviewing request parameters |
| 404 | SCG_ERROR_4041 | Resource you are trying to update cannot be found for <parameter(s)> | Retry after reviewing parameters |
| 404 | SCG_ERROR_4042 |
No mdn is found. |
Check recipient country and retry after reviewing parameters |
| 404 | SCG_ERROR_4043 | The language code <language> is not found among the languages supported by Google Translate | Retry with existing language code provided |
| 404 | SCG_ERROR_4044 |
Non-shortcode senderId is found. |
Retry after reviewing request parameters |
| 404 | SCG_ERROR_4045 | No sender id matches with recipient country. | Retry after reviewing request parameters |
| 404 | SCG_ERROR_4046 | Access token expired | Retry after reviewing request parameters |
|
|
|||
|
409 |
SCG_ERROR_4090 |
The access token could not be updated because resource is being updated |
Retry after reviewing request parameters |
|
|
|||
|
422 |
SCG_ERROR_4220 |
Attachment content could not be downloaded from the provided URL. The error message is <error message> |
Please review the error message details and retry after taking corrective action. Please contact Syniverse Support in case the problem persists |
|
|
|||
|
500 |
SCG_ERROR_5000 |
Unexpected Server Error |
Retry after some time. If problems persists, please contact Syniverse support |
| 500 | SCG_ERROR_5001 | Unexpected Non Retriable Server Error | Please contact Syniverse Support |
| 500 | SCG_ERROR_5002 | Message type restriction not implemented for: <messageType> |
Please contact Syniverse Support |
| 500 | SCG_ERROR_5003 | Error redirecting to proxy: <parameter> | Please contact Syniverse Support |
| 500 | SCG_ERROR_5004 | Error downloading attachment from storage: <parameter> | Please contact Syniverse Support |
|
|
|||
| 503 | SCG_ERROR_5030 | Service Unavailable | Retry after some time. If problems persists, please contact Syniverse support |
SCG Failure Error Notifications
These are error codes sent asynchronously via Event Manager.
|
Failure Code |
Failure Details |
|
1001 |
Stale data |
|
1002 |
Invalid Recipient - Please check to make sure you have the correct recipient address/format in your “to” address and retry with correct format |
|
1003 |
No Applicable Sender ID - The SenderId is not applicable for this message. Please select the correct SenderId and retry. |
|
1004 |
Forbidden Phrase - The message has a forbidden phrase. Please retry after removing the phrase |
|
1005 |
No Consent - Subscriber has not consented to receive the message. |
|
1006 |
Could not find template with name <name> - Please retry after fixing message template error. |
|
1006 |
Template config mismatch between channel and senderId - Please retry after fixing template errors. |
|
1006 |
Message does not satisfy any of the senderId validators - Please retry after fixing message template error. |
|
1006 |
Message does not satisfy any of the channel validators - Please retry after fixing message template error. |
|
1006 |
No value provided for variable: <variable> - Please retry after fixing message template error. |
|
1006 |
Validator rule <rule> failed on <variable>:<value> - Please retry after fixing message template error. |
|
1006 |
Validator rule <rule> failed on <message> - Please retry after fixing message template error. |
|
1007 |
Message Expired - Message could not be sent within the expiry time defined. Please resend the message |
|
1008 |
Whitelist Violation - Cannot send message to this recipient who is not in the whitelist. |
|
1009 |
Message could not be delivered to the recipient. If the error persists on retry, please contact Syniverse support. |
|
1010 |
Content refused, type <mimetype>, allowed: <mimetype>, blocked: <mimetype> - Please retry after selecting a different mimetype. |
|
1011 |
Duplicate key - If the error persists on retry, please contact Syniverse support. |
|
1012 |
Message size <size> exceeds max allowed size <size> - Please retry after reducing the message size. |
|
1014 |
Message encoding failed, tried: <encoding> - Please retry after removing the message contents that are not supported by encoding. |
|
1015 |
Invalid sender address - Please retry after selecting a valid sender address |
|
1016 |
Invalid/illegal character in url: <character> - Please retry after removing illegal characters in the url |
|
1017 |
Invalid Dynamic Group definition |
|
1018 |
Message assembly failure - If the error persists on retry, please contact Syniverse support. |
|
1019 |
Attachment size <size> exceeds max allowed attachment size <size> - Please retry after reducing the attachment size. |
|
1020 |
Invalid Tracking URL - Please retry after fixing the tracking URL. |
|
1021 |
Invalid sender address credentials - Please retry after correcting sender address credentials. |
|
1022 |
Failed price threshold. Unknown price. - Please contact Syniverse support. |
|
1022 |
Failed price threshold - current price <price>, price threshold <price> - Please contact Syniverse support. |
|
1023 |
Indexed field too long - Please contact Syniverse support. |
|
1024 |
Translate failed - Please contact Syniverse support. |
|
1025 |
Invalid social handle - You are trying to create/update contact with empty social_handles. Please retry after specifying the correct social handle. |
|
1026 |
Too many recipients - You have exceeded maximum allowed recipients count in your message request. Please retry after reducing the number of recipients. |
|
1027 |
No Sender ID suitable for auto purchase - There is no suitable sender for the provided alias. Please use the correct alias and resend the request. |
|
1028 |
Storage quota exceeded - Please contact Syniverse support |
|
1029 |
Contacts quota exceeded - Please contact Syniverse support |
|
1030 |
Too many recipients in one batch - You are trying to send message to more than allowed amount of recipients. Please retry after reducing the recipients in the batch. |
|
1031 |
Illegal SMTP header value - There is invalid character in your message. Please retry after changing the message body to remove invalid character. Contact Syniverse Support , if problem persists. |
|
1032 |
Invalid registered delivery flag - Please contact Syniverse support |
|
1033 |
System error from remote service - Please contact Syniverse support |
|
1034 |
Invalid service type - Please contact Syniverse support |
|
1035 |
Command length is invalid - Please contact Syniverse support |
|
1036 |
Wrong state for command - Please contact Syniverse support |
|
1037 |
Invalid message id - Please contact Syniverse support |
|
1038 |
Outgoing queue is full - Please contact Syniverse support |
|
1039 |
Throttling error - The message exceeds throttling limit. If the error persists on retry, please contact Syniverse support. |
|
1040 |
Invalid scheduled delivery time - Scheduled delivery time is either the incorrect length or is invalid. Please retry message after fixing the schedule delivery time. |
|
1041 |
Submitting message has failed - Please contact Syniverse support |
|
1042 |
Invalid source address type of number - Source address is invalid. Please retry after fixing the source address. |
|
1043 |
Invalid destination address type of number - Destination address is invalid. Please retry after fixing the destination address. |
|
1044 |
Invalid number of messages - Please contact Syniverse support |
|
1045 |
Invalid Validity Period - Please retry after changing the validity period in the request to the correct format. |
|
1046 |
Message was rejected - If the error persists on retry, please contact Syniverse support. |
|
1047 |
Permission denied - Please check the message content to see if it is supported. Please contact Syniverse support in case you have any questions. |
|
1048 |
Invalid data coding scheme - Please contact Syniverse support |
|
1049 |
Invalid request - Please contact Syniverse support |
|
1050 |
Multiple addresses not supported - This request does not support multiple addresses. |
|
1051 |
Validation error - Message validation failed. Please contact Syniverse support |
|
1053 |
Failed to upload media URL - If the error persists on retry, please contact Syniverse support. |
|
1054 |
Failed to download media URL - If the error persists on retry, please contact Syniverse support. |
|
1055 |
Too many records in set - Please refine report query parameters to reduce number of records. Please contact Syniverse support in case you are not able to do that. |
|
1056 |
Recipient Number is Deactivated - Please change recipient number and retry . |
|
1057 |
Failed to provision number in ZipWhip - Please change recipient number and retry. |
|
1058 |
Message Scheduled Time too far ahead. - Please change Message Schedule time and retry. |
|
1059 |
Timed out - If the error persists on retry, please contact Syniverse support. |
|
1060 |
Inactive user - Please change user and retry. |
|
1061 |
Delivery Window Restriction Violation - Please retry sending message making it meets delivery window restriction. |
|
1062 |
Daily Quota Restriction Violation - If the error persists on retry, please contact Syniverse support. |
|
1063 |
Gateway Error - If the error persists on retry, please contact Syniverse support. |
|
1064 |
Recipient with multiple addresses - Please the number of recipient addresses and retry. |
|
1065 |
Message restricted by upstream provider - Please contact Syniverse support. |
|
1066 |
Message delivery failure due to invalid Message. Message expired/deleted/rejected by External Entity - Please contact Syniverse support. |
|
1067 |
Too many messages to the same MSISDN - Please contact Syniverse support. |
|
1201 |
No answer If the error persists on retry, please contact Syniverse support |
|
1202 |
Call rejected - If the error persists on retry, please contact Syniverse support |
|
1203 |
Temporary failure reaching recipient - If the error persists on retry, please contact Syniverse support |
|
1204 |
Recipient busy - If the error persists on retry, please contact Syniverse support |
|
1205 |
Invalid phone number quantity - Please reduce the number of phone number and retry request. |
|
1206 |
Phone number doesn't exist - Please retry request after validating and changing phone number. |
|
1207 |
Failed to delete the phone number - If the error persists on retry, please contact Syniverse support |
|
1208 |
Call id not found - Please contact Syniverse support |
|
1209 |
Recording is already started - Please contact Syniverse support |
|
1210 |
Billing error: Account not found - Please contact Syniverse support |
|
1211 |
Billing error: Rate not implemented - Please contact Syniverse support |
|
1212 |
Document not found - Please contact Syniverse support |
|
1213 |
DirectLine request failed - Please contact Syniverse support |
|
1214 |
Invalid sender route - Please contact Syniverse support |
|
1215 |
Encryption failed - Please contact Syniverse support |
|
1216 |
AV Scan Failed - The attachment / media URL did not pass Anti Virus Scan. Please change the attachment/media URL and retry the request. |
|
1220 |
Calls referenced cannot be part of the same bridge or conference - Please contact Syniverse support |
|
1225 |
Sender Id does not support verifiedSMS - Please review Sender Id and retry the request. |
SMPP Error Codes returned by SCG
|
Status Info |
SMPP Code |
SCG Status Code |
Description |
Status Origination |
INTERIM OR TERMINAL |
Success/Fail |
|
ACCEPTED/BUFFERED |
4 |
Not Supported |
External entity confirmation/Message buffered by the external entity |
Syniverse |
INTERIM |
Success |
|
DELIVERED TO CARRIER |
3 |
200 |
Message sent for Delivery (Does not indicate that it was delivered to the Carrier). |
Syniverse |
INTERIM |
Success |
|
DELIVRD |
0 |
200 |
Delivered to Device by the external entity |
Carrier |
TERMINAL |
Success |
|
BAD ADDRESS |
90 |
1002 |
Invalid or Incorrect destination address - Syniverse generated |
Syniverse |
TERMINAL |
Fail |
|
CARRIER GATEWAY ERROR |
93 |
Not Supported |
External entity not responding - Syniverse will re-attempt delivery |
Syniverse |
INTERIM |
Fail |
|
DELETED |
5 |
1066 |
Message deleted by the external entity |
Carrier |
TERMINAL |
Fail |
|
EXPIRED |
8 |
1066 |
Message expired by the external entity |
Carrier |
TERMINAL |
Fail |
|
INTERNAL ERROR |
98 |
500 |
Internal Error - Syniverse generated. Customer to retry delivery |
Syniverse |
TERMINAL |
Fail |
|
INVALID ROUTING |
91 |
1015 |
Invalid or Incorrect routing - Syniverse generated |
Syniverse |
TERMINAL |
Fail |
|
INVALID TEMPLATE ID |
29 |
Not Applicable |
Invalid Template Id - Syniverse generated |
Syniverse |
TERMINAL |
Fail |
|
INVALID TEMPLATE PARAMETERS |
27 |
Not Applicable |
Invalid Template parameters - Syniverse generated |
Syniverse |
TERMINAL |
Fail |
|
INVALID TEMPLATE TYPE |
28 |
Not Applicable |
Invalid Template type - Syniverse generated |
Syniverse |
TERMINAL |
Fail |
|
REJECTD |
23 |
1066 |
External entity error - Message rejected by the external entity |
Carrier |
TERMINAL |
Fail |
|
TEMPLATE NOT SUPPORTED |
30 |
Not Applicable |
Template not supported - Syniverse generated |
Syniverse |
TERMINAL |
Fail |
|
Message Validity Expired |
34 |
Not Applicable |
Validity Period expired for MT message as per Validity Period parameter received |
Syniverse |
TERMINAL |
Fail |
|
REJECTD |
35 |
Not Applicable |
Invalid Campaign ID rejected by the carrier |
Carrier |
TERMINAL |
Fail |
|
UNDELIV |
7 |
Not Applicable |
Retry Exceeded - Syniverse will not attempt further retries. |
Syniverse |
TERMINAL |
Fail |
|
UNDELIV |
9 |
1066 |
External entity error - Failed due to NDNC Blacklist or Registration failed |
Carrier |
TERMINAL |
Fail |
|
UNDELIV |
90 |
1066 |
Invalid Number - Carrier generated |
Carrier |
TERMINAL |
Fail |
|
UNDELIV |
181 |
1067 |
External entity error - Too many messages to same MSISDN |
Carrier |
TERMINAL |
Fail |
|
UNDELIV |
190 |
1066 |
External entity error -Mobile Equipment Error |
Carrier |
TERMINAL |
Fail |
|
UNDELIV |
191 |
1066 |
Sender Blocked |
Carrier |
TERMINAL |
Fail |
|
UNDELIV-INTERIM |
184 |
Not Supported |
Intermediate Status PENDG-ABS-SUB : Message will be retried by carrier |
Carrier |
INTERIM |
Fail |
|
UNDELIV-INTERIM |
185 |
Not Supported |
Intermediate Status PENDG-MEMEXCD: Message will be retried by |
Carrier |
INTERIM |
Fail |
|
UNDELIV-INTERIM |
186 |
Not Supported |
Intermediate Status PENDG-NW-FAILR: UNDELIV- Message will be retried by carrier |
Carrier |
INTERIM |
Fail |
|
UNDELIV-INTERIM |
187 |
Not Supported |
Intermediate Status PENDG-NWTMOUT: Message will be retried by carrier |
Carrier |
INTERIM |
Fail |
|
UNDELIV-INTERIM |
188 |
Not Supported |
Intermediate Status PENDG-SMSTMOUT:Message will be retried by carrier |
Carrier |
INTERIM |
Fail |
|
UNDELIV-INTERIM |
189 |
Not Supported |
Intermediate Status PENDG-HDSTBUSY: Message will be retried by carrier |
Carrier |
INTERIM |
Fail |
|
UNKNOWN |
999 |
Not Applicable |
Unknown status returned by the external entity |
Carrier |
TERMINAL |
Fail |
Voice Calling
1. Voice Calling API Errors
|
Error Code |
Error Description |
Http Code |
|
403 |
No admin access to this API |
403 |
|
403 |
Access denied for sender ID: <id> |
403 |
|
403 |
Forbidden access to call service maintenance. |
403 |
2. Voice Calling Failure Errors
|
Failure Code |
Failure Details |
|
1052 |
Invalid call state <state> |
|
1201 |
No answer |
|
1202 |
Call rejected |
|
1203 |
Temporary failure reaching recipient |
|
1204 |
Recipient busy |
|
1205 |
Invalid phone number quantity |
|
1206 |
Phone number doesn't exist |
|
1207 |
Failed to delete the phone number |
|
1208 |
Call id not found |
|
1209 |
Recording is already started |
A2P SMS Failure Errors
|
SCG Error Code |
SCG Error Description |
|
1002 |
Invalid Recipient |
|
1015 |
Invalid sender address |
|
1038 |
Outgoing queue is full |
|
1039 |
Throttling error |
|
503 |
Service Unavailable |
|
1046 |
Message was rejected |
|
1012 |
Message Too big |
|
1035 |
Command length is invalid |
|
1036 |
Wrong state for command |
|
1037 |
Invalid message id |
|
1040 |
Invalid scheduled delivery time |
|
1032 |
Invalid registered delivery flag |
|
1033 |
System error from remote service |
|
1034 |
Invalid service type |
|
1026 |
Too many recipients |
|
1041 |
Submitting message has failed |
|
1042 |
Invalid source address type of number |
|
1042 |
Invalid source address type of number |
|
1043 |
Invalid destination address type of number |
|
1043 |
Invalid destination address type of number |
|
1044 |
Invalid number of messages |
|
1045 |
Invalid Validity Period |
|
1009 |
Delivery Failure |
|
1047 |
Permission denied |
|
1047 |
Permission denied |
|
1047 |
Permission denied |
|
1048 |
Invalid data coding scheme |
|
402 |
Insufficient credit |
A2P MMS Errors
|
SCG MMS Error Code |
SCG Error Description |
|
1015 |
Invalid sender address |
|
1015 |
Invalid sender address |
|
1010 |
Content Refused |
|
1012 |
Message Too big |
|
503 |
Service Unavailable |
|
1049 |
Invalid request |
|
1047 |
Permission denied |
|
1046 |
Message was rejected |
|
1050 |
Multiple addresses not supported |
|
1041 |
Submitting message has failed |
|
1051 |
Validation error |
P2P MMS Errors
|
SCG MMS Error Code |
SCG Error Description |
|
1002 |
Invalid Recipient |
|
503 |
Service Unavailable |
|
500 |
Server Error |
Facebook Messenger Errors
|
SCG FB Error Code |
SCG Error Description |
|
1012 |
Message Too big |
|
1002 |
Invalid Recipient |
|
1002 |
Invalid Recipient |
|
400 |
Bad Request |
0 Comments