SMS notifications — automatic, from your own system
An SMS notification does not go out because someone clicks send, but because something happens: an order is confirmed, a parcel leaves the warehouse, an invoice falls due, a server drops out. Connect your webshop, ERP or monitoring to our Belgian REST API — or simply let your system send an email.
A notification is not advertising
The distinction matters, legally as well. A notification belongs to a service the customer requested themselves and is therefore expected. Advertising is unsolicited and requires prior consent. Do not mix the two: a single offer at the bottom of an order confirmation turns that message into a commercial communication after all.
| SMS notification | SMS marketing | |
|---|---|---|
| Trigger | An event in your system | A campaign you start yourself |
| Expected by the recipient | Yes — part of the service they signed up for | No — hence the consent requirement |
| Prior consent | Not required for the operational message itself | Required for private individuals |
| Opt-out in the message | Not needed | Mandatory |
| Typical volume | Continuous, per event | A few campaigns per year |
General information, not legal advice about your situation. If you do want to send commercially, read the guide to SMS marketing.
What do you send automatically?
Orders & delivery
Confirmation, dispatch, ready for collection or a changed time slot.
Invoicing & payment
A payment reminder around the due date, or confirmation of a payment received.
Outages & monitoring
A server, service or machine going down — even when your mail server is the problem itself.
Login & verification
One-time codes for two-step verification, with priority routing.
Appointments
A confirmation on booking and a reminder shortly before the moment itself.
Staff & planning
A changed shift, an urgent call-out or a job being assigned.
Connecting notifications in 4 steps
Choose the events
Decide which events deserve a message — a confirmation, a delivery, a due date, an outage.
Create an API token
Create an API token in your account and, if you wish, restrict it to your server's IP addresses.
Set up the integration
Have your software make a call to the REST API on every event, or send an email via Mail2SMS if an API is not an option.
Feed statuses back
Set up a webhook so the delivery status of every message returns automatically to your own system.
Integration is always possible — even without an API
REST API. One HTTP call per message. There are code samples for PHP, Python, Node.js, C#, PowerShell and cURL, an OpenAPI specification, a Postman collection and an official PHP SDK on GitHub. Operational in minutes.
Mail2SMS. If your system cannot call an API but can send email — which is the case with many monitoring, accounting and ERP packages — it simply sends an email and we convert it into an SMS.
Off the shelf. For WordPress and Zapier, ready-made integrations already exist, so no code is involved at all.
Arriving is the whole point
With a notification, delivery is not a detail: an outage alert that fails to arrive is worse than no alert at all. That is why messages go out over direct Belgian operator connections, with priority routing for time-critical messages such as verification codes. Every message gets an individual delivery status you can consult, or have sent back automatically to your own system via a webhook. The infrastructure runs on Belgian servers with 99.99% uptime.
