Introduction

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 phone numbers. Texter will be able to give you an indication if your supplier is returning fake DLRs, if the route to your recipient might be a grey route, and more.

❗️

Note

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 when using the API you are responsible for sending your own messages, this means you will have to perform the content comparison yourself. Whereas when using the dashboard version, Texter will send the messages immediately using one of the connections you configured.
Having control of both the sent content and received content, the dashboard version will show you what got sent out, as well as what arrived on the mobile device, and the differences. The API can only show you what arrived on the mobile device, you need to send the test messages yourself.

Prerequisites

To make use of our Texter API you need to be registered at CM.com and you need to have access to the Texter app.

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

How it works

To use Texter, you supply the 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 will send.
After we give you the phone number, it will be your responsibility to send the SMS message. The Texter API doesn't send the SMS for you

After you send the test message with the supplied text and key, we provide you with the details of the delivery status on the mobile device. Details include whether the message has arrived, when it arrived and the received text body.
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.

The Texter system will provide test nodes that have a good and stable internet connection, we cannot guarantee that we have such a node for each operator. In those cases where we don't, the test node doesn't always report back immediately.

📘

Delayed Test Results due to Network Conditions

In some cases, the result from our test node may be delayed and received several hours after you’ve sent your test message due to slow internet connections. Even if the result comes through later than expected, we will still forward it to your callback API.