TonPing forwards SMS and notifications from the apps you choose, on an Android phone, to your webhook, by rules you set, and tells you when that phone stops working.
Messagesjust now
ALERT-SMS
Power cut in server room. Backup power on since 13:04
Delivered to webhook · 200
{
"event_id": "4b1c6f0e-3a52-4d0b-9a77-0e2f5c1d8a11",
"type": "message.received",
"created_at": "2026-11-07T06:05:00.123Z",
"device": {
"name": "Office phone"
},
"message": {
"source": "sms",
"sender": "ALERT-SMS",
"body": "Power cut in server room. Backup power on since 13:04",
"received_at": "2026-11-07T06:04:59.5Z",
"recovered": false
}
}Some fields left out for reading. Every field is in the webhook guide
Install TonPing on the Android phone that receives the messages and make it the default SMS app. A spare phone that only receives messages works best.
Enter the https URL of your system, then set rules for what to forward: sender or app, words that must appear, words that must not.
Matching messages go out as JSON, and every request carries an HMAC signature. The raw text is sent character for character; your system decides what to do with it.
SMS from any sender and notifications from the apps you pick go to your webhook as raw text, character for character, to use however you like. App notifications are optional and off by default.
Android hands SMS straight to the default SMS app, so TonPing runs as that app and takes care of the usual reasons background apps stop working.
Built so messages are not lost when the network drops: they queue on the phone and go out when it is back. If your endpoint is down, the server retries for up to 24 hours with the same event_id, so your system can skip duplicates.
The phone checks in every 5 minutes. If it stays quiet for more than 15 minutes, your webhook hears about it, so nobody has to notice that messages stopped coming.
device.offlinedevice.onlineDifferent kinds of messages arrive at the same URL: an alert SMS from equipment, a new-order notification from a shop app, a message from a customer, a payment SMS. Each request is a JSON POST with an HMAC signature so your system can check it came from TonPing.
A monthly subscription through Google Play. Pick by how many phones receive messages.
7-day free trial for new subscribers
Yearly plans cost 10 months
SMS from any sender you set a rule for, and notifications from the apps you choose. Notifications are optional, off by default, and less certain than SMS, because a notification that was swiped away cannot be recovered.
Anything your system needs to know about when a message arrives: SMS from devices, new-order notifications, messages from customers, or payment alerts. TonPing sends the raw text; your system decides what to do.
You need your own webhook on HTTPS. The guide includes a sample webhook receiver in PHP.
Android delivers SMS directly to the default app, and Google Play requires it for apps that read SMS. That is why we suggest a spare phone that only receives messages.
Yes, only the messages that match your rules; everything else stays on the phone. They travel over an encrypted connection, are kept for 90 days and then deleted automatically, and are never sold. The privacy policy has the details.
Messages wait in the queue on the phone and go out when the server is back. They arrive late, but they are not lost.