Texter is an SMS-route quality testing tool that uses live nodes.

With Texter, we aim to provide you with a testing method, that minimizes testing inaccuracies. For example the “whitelisting” of numbers. Texter will give you and indication of whether or not your supplier might return fake DLRs, if the route to your recipient might be a grey route, and more.



The Texter API is an additional, programmatic way of using Texter. It allows you to fetch test MSISDNs and a test key, which you need to use to send your own test messages.

Because using the API you are sending your own messages, this means you will have to compare what you sent with what Texter returns yourself. In the dashboard version of Texter, Texter itself will send the messages, using one of the connections you configured.
Because Texter is also sending, the dashboard version will show you what got sent out, as well as what arrived on the handset, and the differences. The API can only show you what arrived on the handset, because you need to send the test messages yourself.


To make use of our Texter API you need to be registered at and you need to be acquired in the Texter app.

You can request access via the contact center on the Texter product page

How it works

To use Texter, you supply us with an operator you want to test. We respond with a phone number and a 16 character key that must be in the SMS test message that you want to send.
After we give you the phone number, it will be your responsibility to send the SMS message yourself. The Texter API doesn't send the SMS for you

After you send your test message with the supplied text and key, we provide you with the details of the potential delivery on the handset. Details such as whether the message has arrived, when it arrived and what has been arrived.
You can receive these test details by providing us with a webhook URL to your own API or you can poll them from the Texter API.

We do our best to provide you with test nodes that have a good and stable internet connection. But it happens sometimes that our live test nodes don't have a perfect stable internet connection. In those cases, the test node can't immediately report back.

It can happen that we receive the result of our test node several hours after you sent your test message due to slow internet connection. Despite receiving a result several hours later, we will still send it to your callback API.