![]() ![]() Your first step depends upon your app account. ![]() The process to obtain an offline short code for your app is described below.Īdd one or more offline short codes as follows. Note: This method is only allowed for a short code that is set up as an offline short code. Note: If the developer's app is expecting a huge number of Mobile Originated (MO) messages, then it is recommended to use the Receive SMS callback by registering a listener URI for the app where the API Gateway immediately delivers the incoming messages as soon as each message arrives in the AT&T Wireless network. The totalNumberOfPendingMessages parameter in the SMS API response indicates that there are any more messages left on the server that are not sent in the current response.Īn app that supports receiving SMS messages must invoke this request at least once every 30 minutes otherwise the messages are automatically removed from the API Gateway.įor apps that expect to receive a lot of SMS messages, it is recommended that the app invokes this request frequently, but with a maximum frequency of one every 5 minutes. If there are more messages than could fit into a single response, the app must invoke multiple method requests to retrieve the complete list of the messages. This method removes the messages from AT&T and therefore it retrieves only those SMS messages received since the previous Get SMS method request. The Get SMS method receives multiple SMS messages sent to the short code associated with the app account from the AT&T Wireless network.Įach time this method is requested all SMS messages are received for the short code associated with the app account. For delivery status of an SMS message you can have a callback or you can poll for the message.When using the GMA One API to send an SMS message from the application, the sender address should always be set to the highest numbered short code available for the application. The GSMA One API can support multiple short codes for an application.For more information, please see the FAQs. The process for on-boarding a custom short code typically takes 1-2 weeks. You can bring your own short code (custom short code) to use for your application.You must register this callback URI during provisioning. By default, an online short code is assigned to your application for the reception of Mobile Originating SMS messages via a callback URI, so that the application gets a notification as soon as a message is received.The RESTful SMS API provided by AT&T requires that you provision your app as follows. Any SMS message that uses the Unicode encoding must be handled by the app by converting the hexadecimal value of the body using the first byte as the key for the encoding.Using the GSMA One API enables you to specify a short code as a parameter in the URI to indicate the originating sender address for the SMS message. If the application wants to use multiple short codes to send SMS messages, then consider using GSMA One API. AT&T supports two signatures of SMS API GSMA One and AT&T.All the messages sent are retried for up to 72 hours and any undelivered messages get deleted after that.You can send an SMS message to a maximum of 10 recipients at a time.The RESTful SMS API provided by AT&T has the following considerations. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |