API FAQ

Yes. The interface is the same as HTTP, so the only change will be in the protocol portion of the URL used (https:// for SSL).

We recommend that HTTP (SSL) is used where ever security and message integrity is required for an application.

Your user ID and password will be provided after you signup. If you need further assistance please contact Support.

No, your password will not expire

Use the password retrieval feature available on the login page

Yes. Although a few networks do not provide the message status information, most do and they will be shown with the message in the Messenger Inbox

No. Standard SMS does not provide this sort of information. The closest you can get is if the carrier notifies us when the message is received on the handset.

Yes. When sending an email set the option for a “read receipt” (each email system has a different way of doing this so see the relevant vendor for more information).

When a message is processed with a read receipt request, Messenger waits for a few minutes and sends an email back that has the status information for each recipient. If you have login credentials you can also view this information in the Messenger Inbox.

Yes. Some languages may not display correctly on some handsets and carrier networks.

If you are using a UTF-16 language (Chinese, Cyrillic etc), your character payload per SMS message part decreases to 70 characters in the first part, and 134 characters in the second part and 201 in the third part.

This means if you send a message that is 100 characters (for example) in a UTF-16 language, you will be charged for 2 messages.

Dialhog attempts to send all messages to the carriers within seconds of receiving them, but SMS is a best effort, store and forward process which means that the carriers may have their own queuing, delivery and expiry policies.

Once Dialhog has passed the message to the carrier delivery is beyond our control, however, we will request status updates and use these to keep you informed of the of the message if these are available.

You can use the status information to decide whether you should resend the message or use an alternative communication method.

If individual (customised) messages are prepared and sent then about 3000 per minute can be sent through the Dialhog API. The speed of message delivery will also be impacted by:

• Network connection speed between your client and Dialhog.
• The destination carrier. Some carriers throttle message delivery based on their network requirements.

The error field contains any string value the carrier returns to us and is very carrier/SMSC/UAS/developer dependent.

Yes. Any replies to messages you send out will also include a messageId that will link the reply to your original message.

The ID provided by your service is a string of up to 36 characters. If you are persisting this information to a database, that would be the field type to use.

No. Not at this time. If you require this feature then contact Sales.

There are two options (Polling and Pushing) to retrieve incoming messages, replies and status updates and it will depend on your network setup, resources and application requirements as to which best suits.

Polling is a client initiated connection to the Messenger API server and reduces firewall and proxy issues that can occur with the push method. More detail available about polling available here

The Push option has the Messenger Server connecting to a REST end point on your server each time a message (reply or status) is processed. More detail about Pushing via Callbacks available here

Before. The URL encoding is required in order for the request to be submitted to the Messenger API. Once we receive it it is decoded and then submitted to the the carrier in a format that they require. If you are not setting a fragmentationLimit on your request then ensure that the message length is less than 160 characters before URL encoding it.

We support Plain-Text and Unicode characters. We do not support Ringtones, IMelody, Operator Logos, or MMS

Yes. The to parameter can be a SPACE Separated List of numbers in International format.. For example: to=6421755427 6178542544 12059955852

Ensure you URLencode the parameters.

Yes. You can send an SMS using Email2SMS through Messenger

All replies to messages sent from Messenger appear in the Inbox in the web site. Replies are attached to the original message in a ‘thread’ so you can keep track of your conversations.

If you have configured a ‘callback url’ messages will also be delivered to your own server.

If you have the Messenger app installed, messages will also be delivered to the app.

If you have ‘forward2mobile’ enabled, messages will be forwarded to your phone.

This is rare but it does occur when the there is a communication glitch between the recipient’s handset and their network, that stops the phone from acknowledging that it has received the SMS.

When this happens the carrier continues to attempt to deliver the same message (as per its store and forward procedures) until it receives an acknowledgment from the phone. This situation results in multiple messages on the handset if the handset does not acknowledge properly (if they all have the same sender number and you are not using short codes then this is probably the situation).

We have found that doing a hard restart of the phone fixes the issue. The recipient should simply pull the battery from the handset, wait a few seconds, reinsert the battery and power the handset up again.

Below are some possible scenarios which can prevent the delivery of messages sending from short codes:

• By default, some mobile service providers in North America block message deliveries initiated from short codes. In such cases, the recipients (i.e. the handset owners) must contact their mobile service provider directly to unlock such blockages.
• Some mobile numbers, which have been ported from one network to another, may also experience non-delivery of short codes messages. In such cases, the previous mobile service provider will reply “STOP ALL” to the sender of all the short codes messages to prevent further deliveries. In such cases, the recipients (i.e. the handset owners) must contact their current and/or their previous mobile service providers directly to unlock such blockages.
• Short codes messages cannot be delivered to recipients using Virtual Numbers, as the sender will be unable to bill the Virtual Numbers holder properly. It is recommended that the recipients to not use Virtual Numbers in such cases.
• Short codes messages will not be delivered if a recipient has previously replied to a sender with any of the following (case insensitive) keywords: stop cancel end quit unsubscribe The delivery of any future short codes message from that sender will be halted. The recipient must contact the sender to resume the deliveries.

Yes. To use this feature please contact Support with details of the numbers you want to use and you will be provided with instructions. Generally this is used when sending via Premium Billed Short Codes rather than the Dialhog default threading range of numbers.

Yes. Some networks do allow you to set a word or string of words as the number recipients see as the sender of an SMS. This is done by setting the from part of the message payload To use this feature please contact Sales with details of the strings you want to use.

Source headers can be any alphanumeric with the following restrictions: + No more than 11 characters in total + Use only alphanumeric characters (eg: a-z or A-Z, or 0-9) + No symbols or spaces.

You can request a copy of the Service Rules from Support. As these are dictated by mobile network providers, they are subject to change.

Please provide an email address that they can be sent to.

Messages are charged when submitted to the carrier.