Error Codes
POL0001
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.
POL0002
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.
- In-App Messaging: Send Message
- SMS v2: Get SMS Delivery Status
- SMS v3: Send SMS
POL0003
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.
- In-App Messaging: Send Message
POL1001
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.
POL1002
POL1009
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.
POL1100
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.
POL1101
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.
POL1102
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.
POL9002
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.
POL9003
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.
- In-App Messaging: Get Message Content
SVC0001
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.
SVC0002
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.
SVC0003
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.
- In-App Messaging v2: Create Message Index Delete Message Delete Messages Send Message Update Message Update Messages
SVC0004
The value specified are not valid addresses for the parameter.
Verify that the values conform to a valid address.
- In-App Messaging v2: Send Message
SVC0015
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.
SVC0016
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.
SVC0017
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.
SVC0018
NENA provider system error.
Verify the input parameters again and retry. If the problem still persists, contact support.
SVC0019
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.
SVC0020
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.
SVC1002
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.
SVC8501
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.
SVC8510
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.
SVC8511
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.
SVC8512
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.
SVC8513
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.
SVC8514
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.
bodybadgateway
API Gateway cannot respond to the request.
Wait a few minutes, and try the request again.
- 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
bodyclient
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.
- OAuth-2 v4: Get Access Token, Get User Authorization, Revoke Token
bodycodemissing
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.
- OAuth 2.0 v4: Get Access Token
bodygrant
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.
- OAuth 2.0 v4: Get Access Token
bodymissingclientid
Missing client_id parameter in the request.
Include the client_id parameter, and try the request again.
- OAuth 2.0 v4: Get Access Token, OAuth 2.0 v4 - Get User Authorization
bodynotoken
The token parameter was not found in the request.
Ensure that the token parameter, with valid token, is included in the request.
- OAuth 2.0 v4: Revoke Token
bodyrefreshtokenmissing
The refresh token is missing in the Get Access Token request.
Add the refresh_token parameter, and try the request again.
- OAuth 2.0 v4: Get Access Token
bodyrequest
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.
- OAuth 2.0 v4: Get User Authorization
bodyscope
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.
- OAuth 2.0 v4: Get Access Token
bodytokentypeunsupported
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.
- OAuth 2.0 v4: Revoke Token
bodyunsupportedgrant
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.
- OAuth 2.0 v4: Get Access Token
uriredirectaccessdenied
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.
- OAuth 2.0 v4: Get User Authorization
uriscope
The API scope value is not correct for the API.
Use the correct API scope value, and try the request again.
- OAuth 2.0 v4: Get User Authorization