You can specify the destination number (the number the message is being sent to) in the addresses parameter. This parameter is an array that enables you to provide a maximum of 10 addresses in one method request. If any address is duplicated, then the message is sent only once to that address. The source number (the sender’s number) cannot be specified in any address.

Read the API documentation to learn more about the Send Message method.

Messages sent from your application will appear on your customers' phone when they have installed the AT&T Messages app onto their device.

Yes, if all of the following are true:

• The user is an AT&T postpaid or Smart-Limits mobile phone customer in good standing or Active status.
• The user's AT&T Wireless account must have SMS messaging enabled.
• The user gives permission for your application to send messages on behalf of the user's mobile device. This is accomplished when the application authenticates.

Yes, once consent is given on the AT&T phone, text messages and multimedia messages can be sent from any type of user interface (Web application, iOS or Android application, and so on) to any mobile phone in the USA.

When your message includes the following, then AT&T sends it as an SMS message.

• Text only using the ISO-8859-1 character set.
• No more than 160 characters.
• Is not set up as a group message or 'Reply All' message.

The In-App Messaging API delivers messages to the customers' messaging system. However, whether messages are delivered to the customer's mobile device is dependent on the customer's selected roaming plan.

Yes.

Messages received by your app are also received by the customer's mobile device, so that your customer is able to respond from the interface that is most convenient for the customer.

No.

At this time, your customer will only be capable of sending a message to U.S.A.-based phone numbers.

Yes. The In-App Messaging API can be used by any device for which consent has been given.

Messages sent using the Send Message method will appear to be sent from your customer's AT&T phone number.

See the transaction limits for the various environments. If these limits do not meet your needs, please enter a developer support ticket requesting a revised limit. Depending on your business case, the Support Team may be able to customize the transaction limits.

No. AT&T will send the message for you based on the content of your message; which may include only text, any number of text characters, media attachments, and group messages which allow replies to all recipients.

You will receive a synchronous response with the HTTP Status Code of 201 Created that indicates that the AT&T network has received the message.

No. AT&T will send the message for you based on the content of your message; which may include only text, any number of text characters, media attachments, and group messages which allow replies to all recipients.

Yes. For each user, an index for the user's message inbox has to be created. However, it is recommended to always check the status of the index before trying to create it. Please refer to the In-App Messaging documentation page for more details.

You are able to choose to use either the send or retrieve capabilities depending on which combination best fits the needs for your application.

An index for each user must exist so that your application can interact with the message store for that user. It is an index into a user's message inbox, which adds additional filtering capabilities for message retrieval.

While the delivery time needed for individual messages varies upon factors such as network load and user location; most messages sent to mobile devices that are turned on are delivered quickly, often in seconds.

No, there is no charge for developers to use the In-App Messaging API. At the same time, this API is not meant for Enterprise use.

The In-App Messaging API has two API scopes (IMMN and MIM) that you must select for your application in order to use the full functionality of the API.

• The IMMN scope is applicable if the application is trying to use the Send Message method.
• The MIM scope is used to retrieve messages and/or sync message status updates from an AT&T customer’s Cloud Message inbox (which can be newly provisioned when a user grants consent to the Application).