Sending Messages via HTTP/HTTPS

At aql.com, we're committed to providing trouble-free service. If you're connecting to our gateway, we recommend that you read our backup gateway document. At aql, we run 4 gateways on 2 different networks. The backup gateway document gives examples of how to design your systems to connect to a different gateway in the rare instance that one of our gateways does not respond.

In order to send a message using the gateway, you will need to send a request to one of the following:

• http://gw1.aql.com/sms/sms_gw.php (or https)
• http://gw2.aql.com/sms/sms_gw.php (or https)

The URI-Encoded variables that you will need to pass are:

• username (username of your aql account)
• password (password of your aql account)
• destination (multiple destinations separated by commas - FAQ for how to format numbers)
• message

• originator
• max_concat (limit concatenation)
• sendtime (in the format of "yyyy-mm-dd hh:mm:ss")
• replace_sms (1(one) or 0(zero). - What are Replaceable Messages?)
• flash (1(one) or 0(zero) - What is Flash SMS?)
• dlr_url (HTTP GET delivery report url on your own server)
  
  eg: http://www.site.com/dlr.php?reportcode=%code&destinationnumber=%dest
  %code and %dest are substituted for the real report code and destination number.
  
  %code - the delivery report code. The values are:

  1 = Delivered to Handset
  2 = Rejected from Handset
  4 = Buffered in transit (phone probably off / out of reception)
  8 = Accepted by SMSC
  16 = Rejected by SMSC
  

  %dest - the destination number

Returned is a string consisting of (without leading and trailing quote):
"<status no>:<no of credits used> <description>" - eg: 2:0 Authentication error

The status corresponds to one of the following:

0: SMS successfully queued
1: SMS queued partially
2: Authentication error
3: Destination number(s) error
4: Send time error
5: Insufficient credit or invalid number of msg/destination
9: Undefined error

Classes and Extensions

• aql SMS - CPAN Pearl Class
• aql SMS - PEAR Class