API Reference – Special Characters

We've noticed that some messages have been sent via our API which contained characters that wouldn't get through the carriers and delivered to the phone. Unfortunately, in some cases these invalid characters were also causing some issues with our queueing system and were resulting in some messages getting stuck in the queue.

So we've decided to put through an update in our API, to let you know when you may have sent some messages with invalid characters, allowing you to update the message text on your side, rather than have the message fail.

Here's what our February 2013 API update includes:

1. A new API response code.

  • 532 : Rejected; Your message content has invalid characters. Please check your message text.

2. An explanation of the valid characters for the "MESSAGE_TEXT" parameter. Here's what we've added:


Please note that only the following list of ASCII characters will be allowed, all other characters will result in a ‘532’ error response:

  • a-z
  • A-Z
  • 0-9
  • ~!@#$%^&*()-_=+][?<>,’.”;:/\{}
  • (whitespace)


Also, we've updated our online help centre article to include the above changes. If you have any questions about our API, drop us an email on support(at)

Create a

Password must be minimum 8 charactes. Must contain 1 Uppercase, 1 Lowercase, 1 Number, 1 Special Character