Delivery reports and replies do not reach my webhook

When delivery reports or incoming SMS (replies) do not reach your webhook, the cause is usually in the application settings in the portal or on your server. Below is how to find the problem and what to send to support if that does not help.

Is the webhook set on the right application?

The webhook is set separately for each application (API). If you send through several applications or wallets, check the one your messages actually go through.

1. In the portal, open Modules & APIs.
2. Under My APIs and Modules, open the application card.
3. On the Settings tab, check the Delivery reports tile in the Web hooks section.

If the tile shows You have no settings., no webhook is set. The procedure is in Webhook.

Is "report only on error" turned on?

The Report only when error occurs option sends a delivery report only for failed messages. Nothing arrives for delivered messages. If you want all delivery reports, turn the option off.

Are you expecting the right data format?

• Default mode: one request per message, using GET. The format is described in Delivery confirmations.
• Bulk DLRs - bulk request: a batch of records using POST with application/json. The format is described in Bulk delivery confirmations.

If your server expects a different format, the request arrives but your application does not process it.

Does your server respond correctly?

• The address must be reachable from the internet and start with http:// or https://.
• The server must respond quickly and with the status code 200. Slow or failing processing holds up the delivery of further reports. Push heavy work onto a queue and acknowledge the request right away.
• A firewall or bot protection must not block our requests. Check your server logs: did the requests arrive, and with what response?

Why are incoming SMS not arriving?

Replies only arrive when the message went out with a sender type that supports two-way SMS in the recipient's country. More in Dedicated SMS number and receiving replies. With your own number and Mobile Connect, replies go to your phone, not to the webhook.

What to send to support

If you have gone through the points above and the data still does not arrive, write to us through the contact form with the subject API and send:

• the message ID of the original message (see Message ID,
• the URL you have set for delivery reports,
• for incoming SMS, a screenshot from the phone showing the time and text of the reply,
• what you see in your server log: the request did not arrive, or it arrived with an error?

Frequently asked questions

How do SMS delivery reports work?

A delivery report (delivery confirmation) tells you what happened to the message in the operator's network: whether it was delivered or not. BulkGate stores the status with the message, so you can see it in the message history in the portal. If the application has a webhook set for Delivery reports, the report is also sent to your URL. Confirmations usually arrive within minutes. What each status means is described in Message not delivered.

Which IP addresses does the webhook come from?

If you need to allow our servers in your firewall, write to us with the subject API.

Can I receive delivery reports by e-mail?

With the Email > SMS interface, delivery reports go by e-mail to Email delivery reports, not to a URL.