Watching for new messages inside the SMSEagle web interface means someone has to go look. Webhooks push SMS events straight into your own systems, so they react without anyone checking a screen.
Every incoming SMS, message status change or call reaches your system the moment it happens, with no one watching SMSEagle.
If your system is briefly unavailable, SMSEagle keeps retrying for up to 24 hours.
A built-in test checks the destination address before a real alert depends on it.
Every rule, one screen
Create, review, and toggle all your webhook rules without digging through separate settings screens.
Confirm it works before it matters
Set the target URL and HTTP method, then use the built-in connection test to confirm delivery works before a real event depends on it.
Only the events you need
Limit webhooks to a specific phonebook contact group or to messages containing a given string, instead of firing on every single message.
Guard against spoofed requests
Add an API key parameter and define the expected HTTP status code, with self-signed SSL support if your endpoint needs it.
No event lost during a brief outage
A failed delivery is retried at the interval you set, for up to 24 hours, so a brief outage on the receiving end has a chance to recover first.
SMSEagle hardware SMS gateway
SMSEagle combines hardware and software into a single, self-contained gateway. It is designed for critical environments, so security is built in from the ground up, confirmed by CE, FCC, ISED, UKCA, PTCRB, RCM, IMDA, TDRA, CB Scheme, GCF, carrier certifications (Verizon, AT&T) and ISO 27001.
An incoming SMS or MMS, a status change on an outgoing message (sent, delivered, or error), or an incoming voice call.
As many as you need. Each rule can be enabled or disabled independently.
If the endpoint returns a status code other than the expected one, or no response at all, SMSEagle retries at your configured interval for up to 24 hours.
Yes. Set the trigger condition to a specific phonebook contact group, or to messages containing a given string.
Yes, self-signed SSL is supported for webhook destinations.
Yes, with an API key parameter and a defined expected HTTP status code. Dedicated support is also built in for POST (3CX) and POST (Zabbix), so you can acknowledge a Zabbix alert with an SMS reply such as ACK 12345.
