|
<< Click to Display Table of Contents >> HTTP Interface Overview |
![]() ![]()
|
Overview
AT&T GSMS’s HTTP Interface provides a 2-way interface for the transmission and receipt of SMS messages.
Customers can be authorized to send or receive messages using this HTTP interface. Both HTTP and HTTPS are supported.
This interface can be used either in the form of HTTP POST or as URL (HTTP GET). Only the GET method is used to deliver messages.
Access and Security
All send commands require authentication, implemented via HTTP Basic Authentication. Since Basic Authentication is inherently insecure (e.g. username and passwords sent as clear-text over the Internet and therefore open to interception by a third party), an SSL secured interface can be used.
For further security VPN connectivity may also be made available.
Additional security policies can be applied to authorize your connection based on your application's Source IP address.
Your Account Executive/Support Team will provide with IP address and TCP Port details of the AT&T GSMS to which to connect.
AT&T GSMS provides additional resilience for WSDL interface through active monitoring and failover to maintain your service continuity.
Functionality
AT&T GSMS HTTP Interface implements the following features:
•2 Way SMS Messaging, including Receive from
•1900 Numbers
•Sending in Batches or One-by-One
•Sending WAP Push Messages
•Sending MMS Messages (utilising content type templates for presentation simplification)
•Delivery Reports (Registered Delivery)
•Sending Plain Text
•Messages / WAP Push (SI/SL)
•Ringtones
•Query Message Status and Cancel a Message
•Supports Scheduling Message Delivery
•Supports Defining Validity Period
•Enables the response message to be provided as XML or standard response
•Inbound HTTP (SMS-MO to Application) can be configured as HTTP POST or HTTP GET.
Further Information can be found in the AT&T GSMS HTTP / WSDL Interface Developer's Guide (PDF) available from your account representative.