AT&T Developer
  • Products
  • Resources
  • Blog
  • Sign In

Error Codes


HTTP Status Code
Error Code
Error Message

SEARCH

RESET SEARCH

SHOW FILTER
HIDE FILTER
RESET FILTERS

FILTER

Filter by API

Error Type

RESET FILTERS

400 Bad Request
401 Unauthorized
403 Forbidden

POL0001
A policy error occurred. Error code is

POL0001


Error Code
POL0001

Error Message
A policy error occurred. Error code is

Error Description
The error code (error_message) was returned from the API Gateway on behalf of the API. For more information, see the Possible Causes & Solutions section.

HTTP Status Code

400 Bad Request
401 Unauthorized
403 Forbidden


Possible Causes & Solutions

Authorization parameter is missing (HTTP 400).
Verify that the Authorization parameter is specified in the request header using the following format.
Format: Bearer {{OAUTH_ACCESS_TOKEN}}
Example: Bearer xyz123456789

Authorization parameter value is incorrect (HTTP 401).
Verify that the correct Authorization value (Bearer xyz123456789) is passed. Verify that the API scopes used for generating the access token are accurate, and then regenerate a new or refreshed token if needed.

The OAuth access token used in the request is not valid for the API (HTTP 403).
Verify that the access token that was generated has the correct API scope value for the API that is being called.

Too many requests per minute or exceeding quota level per day (HTTP 403).
The API Gateway throttles the requests depending upon your service level. The service level will vary between sandbox and production app accounts. Restrict the number of calls to comply with the quota limits. Refer to https://developer.att.com/support/faqs/att-developer-program-and-api-platform-faqs#what-are-maximum-transaction-rates-for-apis for the quota limits.


Affected APIs
  • In-App Messaging: Create Message Index, Delete Message, Delete Messages, Get Message, In-App Messaging v2 - Get Message Content, Get Message Index Info, Get Message List, Get Messages Delta, Send Message, Update Message, Update Messages
  • SMS v2: Get SMS
  • SMS v3: Get SMS Delivery Status

403 Forbidden

POL0002
Privacy verification failed for address <address_number>

POL0002


Error Code
POL0002

Error Message
Privacy verification failed for address <address_number>

Error Description
Request is not authorized to retrieve information related to the address (address_number). Correct authorization is required by the requester in order to retrieve information.

HTTP Status Code

403 Forbidden


Possible Causes & Solutions

The app is not authorized to access user’s resource.
The app needs to get the proper consent from the user in order to access the resource.


Affected APIs
  • In-App Messaging: Send Message
  • SMS v2: Get SMS Delivery Status
  • SMS v3: Send SMS

403 Forbidden

POL0003
Too many addresses specified in message part <parameter_name>

POL0003


Error Code
POL0003

Error Message
Too many addresses specified in message part <parameter_name>

Error Description
The number of addresses in the parameter (parameter_name) exceeds the maximum number of addresses.

HTTP Status Code

403 Forbidden


Possible Causes & Solutions

Too many recipients specified by the parameter.
The number of people to whom you can send a message is limited to 10. Set the parameter value to a maximum of 10 addresses. If you need to send this message to more than 10 people, then try sending multiple messages by limiting addresses to 10 people at a time.


Affected APIs
  • In-App Messaging: Send Message

403 Forbidden

POL1001
Channel already exists. %1

POL1001


Error Code
POL1001

Error Message
Channel already exists. %1

Error Description
A channel is already created for your app or you specified a read-only parameter in the request.

HTTP Status Code

403 Forbidden


Possible Causes & Solutions

A channel is already created for your app.
Use the channel ID from the error message. There is no need to create a new channel.

An attempt was made to modify a read-only parameter.
Remove all the read-only parameters from the Update Notification Subscription method and make the request again.


Affected APIs

403 Forbidden

POL1002
No Callback URL set up

POL1002


Error Code
POL1002

Error Message
No Callback URL set up

Error Description
The callback URL is not set up in the AT&T Developer Program website.

HTTP Status Code

403 Forbidden


Possible Causes & Solutions

Affected APIs

403 Forbidden

POL1009
User has not been provisioned for the <api_name>

POL1009


Error Code
POL1009

Error Message
User has not been provisioned for the <api_name>

Error Description
The user is not provisioned for the API (api_name) request. The user needs to be provisioned as a prerequisite for this API.

HTTP Status Code

403 Forbidden


Possible Causes & Solutions

In-App Messaging API : The user's inbox has not been set up.
Wait a few minutes before sending the request again. Typically it takes only a few seconds to provision the inbox, although occasionally there are times when it might take a bit longer due to a heavy load.


Affected APIs
  • In-App Messaging: Create Message Index, Delete Message, Delete Messages, Get Message, Get Message Content, Get Message Index Info, Get Message List, Get Messages Delta, Send Message, Update Message, Update Messages

403 Forbidden

POL1100
Number of sessions exceeds allowed limit <session_limit>.

POL1100


Error Code
POL1100

Error Message
Number of sessions exceeds allowed limit <session_limit>.

Error Description
The maximum number of sessions (session_limit) was exceeded for the request.

HTTP Status Code

403 Forbidden


Possible Causes & Solutions

For the VN scenario, the session limit specified by the app identifier was exceeded. For the member Account ID scenario, the session limit specified by the organization was exceeded.
For the VN and member Account ID scenarios, contact the Administrator to change these limits. For In-App Calling for Mobile Numbers (ICMN) users, the session limit cannot be changed because that limit is a network setting.


Affected APIs

403 Forbidden

POL1101
OAuth access token already associated.

POL1101


Error Code
POL1101

Error Message
OAuth access token already associated.

Error Description
An OAuth access token must be associated with only one VN or member Account ID user.

HTTP Status Code

403 Forbidden


Possible Causes & Solutions

The OAuth access token is already associated with a VN or member Account ID user.
To obtain a second OAuth access token, use the App Key and App Secret from your app account.


Affected APIs

403 Forbidden

POL1102
Session Id not associated with the token.

POL1102


Error Code
POL1102

Error Message
Session Id not associated with the token.

Error Description
Session ID in the URI is not associated with the OAuth access token.

HTTP Status Code

403 Forbidden


Possible Causes & Solutions

The OAuth Access token that was passed in the request is not mapped to the session ID.
Use the same OAuth access token that was initially passed for the Session Creation method, or use the active OAuth refresh token.


Affected APIs

403 Forbidden

POL9002
Subscription already exists.

POL9002


Error Code
POL9002

Error Message
Subscription already exists.

Error Description
The subscription that you are trying to create already exists for this subscriber.

HTTP Status Code

403 Forbidden


Possible Causes & Solutions

The Developer Hosted Server (DHS) has already created the subscription for this user.
Use the existing subscription ID that you created. Do not create a new subscription.


Affected APIs

403 Forbidden

POL9003
Message content size exceeds the allowable limit.

POL9003


Error Code
POL9003

Error Message
Message content size exceeds the allowable limit.

Error Description
The message attachment size exceeds 1 MB (Mega Byte).

HTTP Status Code

403 Forbidden


Possible Causes & Solutions

A message that is on the user's cloud storage exceeds the size of 1 MB, and cannot be retrieved because of limits on the Get Message Content operation.
This is not a recoverable error. The only action that can be taken is to delete the attachment (part). Going forward, limit the message sizes to be less than or equal to 1 MB.


Affected APIs
  • In-App Messaging: Get Message Content

400 Bad Request

SVC0001
<custom_error_message>

SVC0001


Error Code
SVC0001

Error Message
<custom_error_message>

Error Description
This is a general service error that can have different error messages. There will be specific error messages based on the API. See the Possible Causes & Solutions section for more information.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

Specific Error Message: SMPP-0064 Temporary Error. (SMS API)
SMS API: The message delivery cannot be processed due to a temporary problem. Retry the message at some future point.
Retry the message after waiting for 30 to 60 seconds.

Specific Error Message: SMPP-0066 Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not an AT&T subscriber or is unable to receive SMS messages.
Discard the message. Do not retry.

Specific Error Message: SMPP-000B Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not provisioned as an AT&T subscriber.
Do not retry. Do not send any messages for this number. The number is not an AT&T subscriber.

Specific Error Message: In-App Messaging API
In-App Messaging API: User's mailbox index cache does not exist.
Call the Create Message Index method, wait for the inbox cache to be created, and make the initial call again.

Specific Error Message: A service error has occurred. Error code is <error_explanation>. (All APIs)
Unknown error occurred at dependent third-party service (enabler).
The solution is dependent on the actual error. Contact our support team with the error message that you received.


Affected APIs
  • In-App Messaging: Create Message Index, Delete Message, Delete Messages, Get Message, Get Message Content, Get Message Index Info, Get Message List, Get Messages Delta, Send Message, Update Message, Update Messages
  • SMS v3: Get SMS Delivery Status, Receive SMS, Send SMS

400 Bad Request

SVC0002
Invalid input value for message part <parameter_name>

SVC0002


Error Code
SVC0002

Error Message
Invalid input value for message part <parameter_name>

Error Description
A required parameter is missing in the request (parameter_name) or a non-valid parameter value is specified. See the Possible Causes & Solutions section for more information.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

Missing mandatory parameter.
One of the mandatory parameters is missing. Refer to the appropriate API documentation to ensure that the required values are being passed.

One of the input parameter values is incorrect.
Refer to the appropriate API documentation to ensure that the proper value is being passed. Examples include a non-numeric value being passed to a parameter that expects a numeric value or a non-date and time value being passed to a parameter that expects a date and time value.


Affected APIs
  • In-App Messaging v2: Create Message Index, Delete Message, Delete Messages, Get Message, Get Message Content, Get Message Index Info, Get Message List, Get Messages Delta, Send Message, Update Message, Update Messages
  • SMS v3: Get SMS Delivery Status, Receive SMS, Send SMS

400 Bad Request

SVC0003
Invalid input value for Message part , valid values are <parameter_values>

SVC0003


Error Code
SVC0003

Error Message
Invalid input value for Message part , valid values are <parameter_values>

Error Description
The input parameter (parameter_name) contains a value (parameter_values) that is not supported.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

An input parameter contains a value that is not part of an allowed values list.
Replace the input parameter (URL variable or message body) value with a value specified in the parameter values specified in this error message. For example, the gender parameter may accept only values such as M or F. If any value other than M or F is passed, then this error is generated.


Affected APIs
  • In-App Messaging v2: Create Message Index Delete Message Delete Messages Send Message Update Message Update Messages

400 Bad Request

SVC0004
No valid addresses provided in the message part <parameter_name>

SVC0004


Error Code
SVC0004

Error Message
No valid addresses provided in the message part <parameter_name>

Error Description
A parameter value (parameter_name) caused the error.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

The value specified are not valid addresses for the parameter.
Verify that the values conform to a valid address.


Affected APIs
  • In-App Messaging v2: Send Message

400 Bad Request

SVC0015
Address is not valid address for E911 routing. Reason <parameter_name>

SVC0015


Error Code
SVC0015

Error Message
Address is not valid address for E911 routing. Reason <parameter_name>

Error Description
Address is not a valid address for E911 routing. The input parameter (parameter_name) is not correct.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

System is unable to geocode the address, which determines the x,y coordinates and maps the address to a PSAP (Public Safety Answering Point).
Verify that the address is a correct postal address and try the request again.


Affected APIs

400 Bad Request

SVC0016
Address confirmation required

SVC0016


Error Code
SVC0016

Error Message
Address confirmation required

Error Description
Address confirmation is required in the request.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

The address provided is routable but no match is found in the Master Street Address Guide (MSAG) database.
Make sure that you are entering a correct civic address. Once you are sure you that the address is correct, set the isAddressConfirmed parameter to True to confirm the address. This will return an e911 location identifier. If the status is pending, then this means the address is in the process of being updated to get this address added to the MSAG database.


Affected APIs

400 Bad Request

SVC0017
<custom_error_message>

SVC0017


Error Code
SVC0017

Error Message
<custom_error_message>

Error Description
This is a general service error that can have different error messages. There will be specific error messages based on the API. See the Possible Causes & Solutions section for more information.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

Specific Error Message: SMPP-0064 Temporary Error. (SMS API)
SMS API: The message delivery cannot be processed due to a temporary problem. Retry the message at some future point.
Retry the message after waiting for 30 to 60 seconds.

Specific Error Message: SMPP-0066 Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not an AT&T subscriber or is unable to receive SMS messages.
Discard the message. Do not retry.

Specific Error Message: SMPP-000B Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not provisioned as an AT&T subscriber.
Do not retry. Do not send any messages for this number. The number is not an AT&T subscriber.

Specific Error Message: In-App Messaging API
In-App Messaging API: User's mailbox index cache does not exist.
Call the Create Message Index method, wait for the inbox cache to be created, and make the initial call again.

Specific Error Message: A service error has occurred. Error code is <error_explanation>. (All APIs)
Unknown error occurred at dependent third-party service (enabler).
The solution is dependent on the actual error. Contact our support team with the error message that you received.


Affected APIs
  • In-App Messaging v2: Create Message Index, Delete Message, Delete Messages, Get Message, Get Message Content, Get Message Index Info, Get Message List, Get Messages Delta, Send Message, Update Message, Update Messages
  • SMS v3: Get SMS Delivery Status, Receive SMS, Send SMS

500 Internal Server Error

SVC0018
NENA provider system error.

SVC0018


Error Code
SVC0018

Error Message
NENA provider system error.

Error Description
National Emergency Number Association (NENA) provider system error.

HTTP Status Code

500 Internal Server Error


Possible Causes & Solutions

NENA provider system error.
Verify the input parameters again and retry. If the problem still persists, contact support.


Affected APIs

400 Bad Request

SVC0019
<custom_error_message>

SVC0019


Error Code
SVC0019

Error Message
<custom_error_message>

Error Description
This is a general service error that can have different error messages. There will be specific error messages based on the API. See the Possible Causes & Solutions section for more information.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

Specific Error Message: SMPP-0064 Temporary Error. (SMS API)
SMS API: The message delivery cannot be processed due to a temporary problem. Retry the message at some future point.
Retry the message after waiting for 30 to 60 seconds.

Specific Error Message: SMPP-0066 Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not an AT&T subscriber or is unable to receive SMS messages.
Discard the message. Do not retry.

Specific Error Message: SMPP-000B Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not provisioned as an AT&T subscriber.
Do not retry. Do not send any messages for this number. The number is not an AT&T subscriber.

Specific Error Message: In-App Messaging API
In-App Messaging API: User's mailbox index cache does not exist.
Call the Create Message Index method, wait for the inbox cache to be created, and make the initial call again.

Specific Error Message: A service error has occurred. Error code is <error_explanation>. (All APIs)
Unknown error occurred at dependent third-party service (enabler).
The solution is dependent on the actual error. Contact our support team with the error message that you received.


Affected APIs
  • In-App Messaging v2: Create Message Index, Delete Message, Delete Messages, Get Message, Get Message Content, Get Message Index Info, Get Message List, Get Messages Delta, Send Message, Update Message, Update Messages
  • SMS v3: Get SMS Delivery Status, Receive SMS, Send SMS

400 Bad Request

SVC0020
<custom_error_message>

SVC0020


Error Code
SVC0020

Error Message
<custom_error_message>

Error Description
This is a general service error that can have different error messages. There will be specific error messages based on the API. See the Possible Causes & Solutions section for more information.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

Specific Error Message: SMPP-0064 Temporary Error. (SMS API)
SMS API: The message delivery cannot be processed due to a temporary problem. Retry the message at some future point.
Retry the message after waiting for 30 to 60 seconds.

Specific Error Message: SMPP-0066 Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not an AT&T subscriber or is unable to receive SMS messages.
Discard the message. Do not retry.

Specific Error Message: SMPP-000B Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not provisioned as an AT&T subscriber.
Do not retry. Do not send any messages for this number. The number is not an AT&T subscriber.

Specific Error Message: In-App Messaging API
In-App Messaging API: User's mailbox index cache does not exist.
Call the Create Message Index method, wait for the inbox cache to be created, and make the initial call again.

Specific Error Message: A service error has occurred. Error code is <error_explanation>. (All APIs)
Unknown error occurred at dependent third-party service (enabler).
The solution is dependent on the actual error. Contact our support team with the error message that you received.


Affected APIs
  • In-App Messaging v2: Create Message Index, Delete Message, Delete Messages, Get Message, Get Message Content, Get Message Index Info, Get Message List, Get Messages Delta, Send Message, Update Message, Update Messages
  • SMS v3: Get SMS Delivery Status, Receive SMS, Send SMS

400 Bad Request

SVC1002
<custom_error_message>

SVC1002


Error Code
SVC1002

Error Message
<custom_error_message>

Error Description
This is a general service error that can have different error messages. There will be specific error messages based on the API. See the Possible Causes & Solutions section for more information.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

Specific Error Message: SMPP-0064 Temporary Error. (SMS API)
SMS API: The message delivery cannot be processed due to a temporary problem. Retry the message at some future point.
Retry the message after waiting for 30 to 60 seconds.

Specific Error Message: SMPP-0066 Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not an AT&T subscriber or is unable to receive SMS messages.
Discard the message. Do not retry.

Specific Error Message: SMPP-000B Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not provisioned as an AT&T subscriber.
Do not retry. Do not send any messages for this number. The number is not an AT&T subscriber.

Specific Error Message: In-App Messaging API
In-App Messaging API: User's mailbox index cache does not exist.
Call the Create Message Index method, wait for the inbox cache to be created, and make the initial call again.

Specific Error Message: A service error has occurred. Error code is <error_explanation>. (All APIs)
Unknown error occurred at dependent third-party service (enabler).
The solution is dependent on the actual error. Contact our support team with the error message that you received.


Affected APIs
  • In-App Messaging v2: Create Message Index, Delete Message, Delete Messages, Get Message, Get Message Content, Get Message Index Info, Get Message List, Get Messages Delta, Send Message, Update Message, Update Messages
  • SMS v3: Get SMS Delivery Status, Receive SMS, Send SMS

400 Bad Request

SVC8501
<custom_error_message>

SVC8501


Error Code
SVC8501

Error Message
<custom_error_message>

Error Description
This is a general service error that can have different error messages. There will be specific error messages based on the API. See the Possible Causes & Solutions section for more information.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

Specific Error Message: SMPP-0064 Temporary Error. (SMS API)
SMS API: The message delivery cannot be processed due to a temporary problem. Retry the message at some future point.
Retry the message after waiting for 30 to 60 seconds.

Specific Error Message: SMPP-0066 Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not an AT&T subscriber or is unable to receive SMS messages.
Discard the message. Do not retry.

Specific Error Message: SMPP-000B Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not provisioned as an AT&T subscriber.
Do not retry. Do not send any messages for this number. The number is not an AT&T subscriber.

Specific Error Message: In-App Messaging API
In-App Messaging API: User's mailbox index cache does not exist.
Call the Create Message Index method, wait for the inbox cache to be created, and make the initial call again.

Specific Error Message: A service error has occurred. Error code is <error_explanation>. (All APIs)
Unknown error occurred at dependent third-party service (enabler).
The solution is dependent on the actual error. Contact our support team with the error message that you received.


Affected APIs
  • In-App Messaging v2: Create Message Index, Delete Message, Delete Messages, Get Message, Get Message Content, Get Message Index Info, Get Message List, Get Messages Delta, Send Message, Update Message, Update Messages
  • SMS v3: Get SMS Delivery Status, Receive SMS, Send SMS

400 Bad Request

SVC8510
<custom_error_message>

SVC8510


Error Code
SVC8510

Error Message
<custom_error_message>

Error Description
This is a general service error that can have different error messages. There will be specific error messages based on the API. See the Possible Causes & Solutions section for more information.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

Specific Error Message: SMPP-0064 Temporary Error. (SMS API)
SMS API: The message delivery cannot be processed due to a temporary problem. Retry the message at some future point.
Retry the message after waiting for 30 to 60 seconds.

Specific Error Message: SMPP-0066 Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not an AT&T subscriber or is unable to receive SMS messages.
Discard the message. Do not retry.

Specific Error Message: SMPP-000B Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not provisioned as an AT&T subscriber.
Do not retry. Do not send any messages for this number. The number is not an AT&T subscriber.

Specific Error Message: In-App Messaging API
In-App Messaging API: User's mailbox index cache does not exist.
Call the Create Message Index method, wait for the inbox cache to be created, and make the initial call again.

Specific Error Message: A service error has occurred. Error code is <error_explanation>. (All APIs)
Unknown error occurred at dependent third-party service (enabler).
The solution is dependent on the actual error. Contact our support team with the error message that you received.


Affected APIs
  • In-App Messaging v2: Create Message Index, Delete Message, Delete Messages, Get Message, Get Message Content, Get Message Index Info, Get Message List, Get Messages Delta, Send Message, Update Message, Update Messages
  • SMS v3: Get SMS Delivery Status, Receive SMS, Send SMS

400 Bad Request

SVC8511
<custom_error_message>

SVC8511


Error Code
SVC8511

Error Message
<custom_error_message>

Error Description
This is a general service error that can have different error messages. There will be specific error messages based on the API. See the Possible Causes & Solutions section for more information.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

Specific Error Message: SMPP-0064 Temporary Error. (SMS API)
SMS API: The message delivery cannot be processed due to a temporary problem. Retry the message at some future point.
Retry the message after waiting for 30 to 60 seconds.

Specific Error Message: SMPP-0066 Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not an AT&T subscriber or is unable to receive SMS messages.
Discard the message. Do not retry.

Specific Error Message: SMPP-000B Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not provisioned as an AT&T subscriber.
Do not retry. Do not send any messages for this number. The number is not an AT&T subscriber.

Specific Error Message: In-App Messaging API
In-App Messaging API: User's mailbox index cache does not exist.
Call the Create Message Index method, wait for the inbox cache to be created, and make the initial call again.

Specific Error Message: A service error has occurred. Error code is <error_explanation>. (All APIs)
Unknown error occurred at dependent third-party service (enabler).
The solution is dependent on the actual error. Contact our support team with the error message that you received.


Affected APIs
  • In-App Messaging v2: Create Message Index, Delete Message, Delete Messages, Get Message, Get Message Content, Get Message Index Info, Get Message List, Get Messages Delta, Send Message, Update Message, Update Messages
  • SMS v3: Get SMS Delivery Status, Receive SMS, Send SMS

400 Bad Request

SVC8512
<custom_error_message>

SVC8512


Error Code
SVC8512

Error Message
<custom_error_message>

Error Description
This is a general service error that can have different error messages. There will be specific error messages based on the API. See the Possible Causes & Solutions section for more information.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

Specific Error Message: SMPP-0064 Temporary Error. (SMS API)
SMS API: The message delivery cannot be processed due to a temporary problem. Retry the message at some future point.
Retry the message after waiting for 30 to 60 seconds.

Specific Error Message: SMPP-0066 Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not an AT&T subscriber or is unable to receive SMS messages.
Discard the message. Do not retry.

Specific Error Message: SMPP-000B Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not provisioned as an AT&T subscriber.
Do not retry. Do not send any messages for this number. The number is not an AT&T subscriber.

Specific Error Message: In-App Messaging API
In-App Messaging API: User's mailbox index cache does not exist.
Call the Create Message Index method, wait for the inbox cache to be created, and make the initial call again.

Specific Error Message: A service error has occurred. Error code is <error_explanation>. (All APIs)
Unknown error occurred at dependent third-party service (enabler).
The solution is dependent on the actual error. Contact our support team with the error message that you received.


Affected APIs
  • In-App Messaging v2: Create Message Index, Delete Message, Delete Messages, Get Message, Get Message Content, Get Message Index Info, Get Message List, Get Messages Delta, Send Message, Update Message, Update Messages
  • SMS v3: Get SMS Delivery Status, Receive SMS, Send SMS

400 Bad Request

SVC8513
<custom_error_message>

SVC8513


Error Code
SVC8513

Error Message
<custom_error_message>

Error Description
This is a general service error that can have different error messages. There will be specific error messages based on the API. See the Possible Causes & Solutions section for more information.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

Specific Error Message: SMPP-0064 Temporary Error. (SMS API)
SMS API: The message delivery cannot be processed due to a temporary problem. Retry the message at some future point.
Retry the message after waiting for 30 to 60 seconds.

Specific Error Message: SMPP-0066 Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not an AT&T subscriber or is unable to receive SMS messages.
Discard the message. Do not retry.

Specific Error Message: SMPP-000B Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not provisioned as an AT&T subscriber.
Do not retry. Do not send any messages for this number. The number is not an AT&T subscriber.

Specific Error Message: In-App Messaging API
In-App Messaging API: User's mailbox index cache does not exist.
Call the Create Message Index method, wait for the inbox cache to be created, and make the initial call again.

Specific Error Message: A service error has occurred. Error code is <error_explanation>. (All APIs)
Unknown error occurred at dependent third-party service (enabler).
The solution is dependent on the actual error. Contact our support team with the error message that you received.


Affected APIs
  • In-App Messaging v2: Create Message Index, Delete Message, Delete Messages, Get Message, Get Message Content, Get Message Index Info, Get Message List, Get Messages Delta, Send Message, Update Message, Update Messages
  • SMS v3: Get SMS Delivery Status, Receive SMS, Send SMS

400 Bad Request

SVC8514
<custom_error_message>

SVC8514


Error Code
SVC8514

Error Message
<custom_error_message>

Error Description
This is a general service error that can have different error messages. There will be specific error messages based on the API. See the Possible Causes & Solutions section for more information.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

Specific Error Message: SMPP-0064 Temporary Error. (SMS API)
SMS API: The message delivery cannot be processed due to a temporary problem. Retry the message at some future point.
Retry the message after waiting for 30 to 60 seconds.

Specific Error Message: SMPP-0066 Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not an AT&T subscriber or is unable to receive SMS messages.
Discard the message. Do not retry.

Specific Error Message: SMPP-000B Invalid Destination Address. (SMS API)
SMS API: The destination address returned in the response is not provisioned as an AT&T subscriber.
Do not retry. Do not send any messages for this number. The number is not an AT&T subscriber.

Specific Error Message: In-App Messaging API
In-App Messaging API: User's mailbox index cache does not exist.
Call the Create Message Index method, wait for the inbox cache to be created, and make the initial call again.

Specific Error Message: A service error has occurred. Error code is <error_explanation>. (All APIs)
Unknown error occurred at dependent third-party service (enabler).
The solution is dependent on the actual error. Contact our support team with the error message that you received.


Affected APIs
  • In-App Messaging v2: Create Message Index, Delete Message, Delete Messages, Get Message, Get Message Content, Get Message Index Info, Get Message List, Get Messages Delta, Send Message, Update Message, Update Messages
  • SMS v3: Get SMS Delivery Status, Receive SMS, Send SMS

502 Bad Gateway

bodybadgateway
Bad gateway

bodybadgateway


Error Code
bodybadgateway

Error Message
Bad gateway

Error Description
The API Gateway could not respond to the request.

HTTP Status Code

502 Bad Gateway


Possible Causes & Solutions

API Gateway cannot respond to the request.
Wait a few minutes, and try the request again.


Affected APIs
  • In-App Messaging v2: Create Message Index, Delete Message, Delete Messages Get Message, Get Message Content, Get Message Index Info, Get Message List, Get Messages Delta, Send Message, Update Message, Update Messages
  • OAuth-2 v4: Event Notification Get Access Token, Get User Authorization, Revoke Token
  • SMS v2: Get SMS, Get SMS Delivery Status, Receive SMS, Send SMS
  • SMS v3: Get SMS, Get SMS Delivery Status, Receive SMS, Receive SMS Delivery Status, Send SMS

401 Unauthorized

bodyclient
{"error":"invalid_client"}

bodyclient


Error Code
bodyclient

Error Message
{"error":"invalid_client"}

Error Description
The provided App Key or App Secret value is not valid.

HTTP Status Code

401 Unauthorized


Possible Causes & Solutions

App Key is deleted and no longer exists.
Do not use deleted App Keys.

App Key is not valid for the API.
Use a valid App Key for the API.

Wrong App Secret used for the API.
Use a correct App Secret for the API.


Affected APIs
  • OAuth-2 v4: Get Access Token, Get User Authorization, Revoke Token

400 Bad Request

bodycodemissing
{ "error":"invalid_request", "description":"Missing code parameter" }

bodycodemissing


Error Code
bodycodemissing

Error Message
{ "error":"invalid_request", "description":"Missing code parameter" }

Error Description
The code parameter value is missing.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

The code parameter is missing in the Get Access Token method request.
Add the code parameter to the Get Access Token method request, and try the request again.


Affected APIs
  • OAuth 2.0 v4: Get Access Token

400 Bad Request

bodygrant
{ "error":"invalid_grant" }

bodygrant


Error Code
bodygrant

Error Message
{ "error":"invalid_grant" }

Error Description
The grant_type parameter value is missing or the value is not valid.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

The grant_type parameter is missing in the request.
Specify the grant_type parameter, and try the request again. The acceptable values for this parameter are: authorization_code, client_credentials, and refresh_token.

The grant_type parameter value is not correct.
Update the grant_type parameter, and try the request again. The acceptable values for this parameter are: authorization_code, client_credentials, and refresh_token.


Affected APIs
  • OAuth 2.0 v4: Get Access Token

400 Bad Request

bodymissingclientid
{ "error":"invalid_request", "description":"Missing client_id parameter" }

bodymissingclientid


Error Code
bodymissingclientid

Error Message
{ "error":"invalid_request", "description":"Missing client_id parameter" }

Error Description
The App Key that is provided for the client_id parameter was not provided in the request.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

Missing client_id parameter in the request.
Include the client_id parameter, and try the request again.


Affected APIs
  • OAuth 2.0 v4: Get Access Token, OAuth 2.0 v4 - Get User Authorization

400 Bad Request

bodynotoken
Missing token parameter

bodynotoken


Error Code
bodynotoken

Error Message
Missing token parameter

Error Description
The access token parameter is missing from the request.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

The token parameter was not found in the request.
Ensure that the token parameter, with valid token, is included in the request.


Affected APIs
  • OAuth 2.0 v4: Revoke Token

400 Bad Request

bodyrefreshtokenmissing
{ "error":"invalid_request", "description":"Missing refresh_token parameter" }

bodyrefreshtokenmissing


Error Code
bodyrefreshtokenmissing

Error Message
{ "error":"invalid_request", "description":"Missing refresh_token parameter" }

Error Description
The refresh_token parameter value is missing in the request.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

The refresh token is missing in the Get Access Token request.
Add the refresh_token parameter, and try the request again.


Affected APIs
  • OAuth 2.0 v4: Get Access Token

400 Bad Request

bodyrequest
{ "error":"invalid_request", "description":"" }

bodyrequest


Error Code
bodyrequest

Error Message
{ "error":"invalid_request", "description":"" }

Error Description
The provided redirect_uri parameter value is not valid.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

Redirect URI does not follow the URI scheme.
Redirect URI should follow the http or https scheme.

Wrong redirect URI is passed in the request.
Use the correct base redirect URI that is assigned to the app account.


Affected APIs
  • OAuth 2.0 v4: Get User Authorization

400 Bad Request

bodyscope
{ "error":"invalid_scope" }

bodyscope


Error Code
bodyscope

Error Message
{ "error":"invalid_scope" }

Error Description
The provided API scope value is missing or the value is not valid.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

API scope value is missing in the request for the OAuth access token.
Add the API scope value, and try the request again.

The API scope value is not valid in the request for the OAuth access token.
Specify a valid API scope value, and try the request again.


Affected APIs
  • OAuth 2.0 v4: Get Access Token

400 Bad Request

bodytokentypeunsupported
Server does not support this type of token.

bodytokentypeunsupported


Error Code
bodytokentypeunsupported

Error Message
Server does not support this type of token.

Error Description
The API Gateway does not support the revocation of the presented token type. The client tried to revoke an OAuth access token on a server not supporting this feature.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

The type of token that was supplied in the request is not able to be revoked.
Supply the correct token type and try the request again.


Affected APIs
  • OAuth 2.0 v4: Revoke Token

400 Bad Request

bodyunsupportedgrant
{ "error":"unsupported_grant_type" }

bodyunsupportedgrant


Error Code
bodyunsupportedgrant

Error Message
{ "error":"unsupported_grant_type" }

Error Description
The provided grant_type parameter value is not supported.

HTTP Status Code

400 Bad Request


Possible Causes & Solutions

Incorrect grant type is in the request.
Specify the correct grant type in the request, and try the request again. The acceptable values for this parameter are: authorization_code, client_credentials, and refresh_token.

Missing the grant_type parameter in the request.
Include the grant_type parameter, and try the request again. The acceptable values for this parameter are: authorization_code, client_credentials, and refresh_token.


Affected APIs
  • OAuth 2.0 v4: Get Access Token

302 Found

uriredirectaccessdenied
redirect_uri?error=access_denied

uriredirectaccessdenied


Error Code
uriredirectaccessdenied

Error Message
redirect_uri?error=access_denied

Error Description
The API Gateway request was not correct or included an API scope value that was not correct.

HTTP Status Code

302 Found


Possible Causes & Solutions

The request was not done using a mobile device on the AT&T Network.
Ensure that the request is done using a mobile device on the AT&T Network.


Affected APIs
  • OAuth 2.0 v4: Get User Authorization

302 Found

uriscope
#error=invalid_scope

uriscope


Error Code
uriscope

Error Message
#error=invalid_scope

Error Description
The provided API scope value is not valid.

HTTP Status Code

302 Found


Possible Causes & Solutions

The API scope value is not correct for the API.
Use the correct API scope value, and try the request again.


Affected APIs
  • OAuth 2.0 v4: Get User Authorization
  • APIS & TOOLS
    • AT&T Video Optimizer
  • APIS & TOOLS
    • Futurist Reports
    • Technical Library
  • SUPPORT
    • Contact Us
    • FAQs
    • Twitter
  • AT&T Developer Program on Github
  • AT&T Developer Program on Facebook
  • AT&T Developer Program on Twitter
AT&T Logo

Terms of Use   Privacy Policy   Your Privacy Choices California Consumer Privacy Act (CCPA) Opt-Out Icon
©2024 AT&T Intellectual Property. All rights reserved

AT&T, the AT&T logo and all other AT&T marks contained herein are trademark of AT&T Intellectual Property and/or AT&T affiliated companies.

14100000
Session Expiring

Your session is about to expire in !

Stay Signed In
Session Expired

Sorry! Your session has expired.

Skip to content