Notes when using our service

URL Encoding

Character encoding

You must url encode your message and orig parameters for more information on url encoding.

You need to ensure the string data (message etc) is UTF-8 encoded and the header is also set to UTF-8. If you start seeing ? in your test messages it will be because of incorrect encoding, probably ISO-8859-1.

Concatenation

Changing the delivery report view

If you exceed 160 characters you automatically covert to concatenation sending, this has the following connotations. Each message consists of a 153 character ‘chunk’ (not 160 chars) the extra characters are used to glue the messages together. Therefore a message that is 307 characters long will require 3 messages to send.HTTPS / SSL Support.

You can also use the API using encryption, just use port 443 or https:// depending on your programming language support.

When you log in to you account and select “reports”=>”delivery reports” by default the data summary is a day by day usage report, if you are using the custom parameter to highlight “groups” or “sub accounts” of usage you can change this default view to one that splits the data into monthly reports based on the parameter you have set.

To do this whilst in your account “Account Settings” => “API Settings” and tick the API Delivery Report View check box.