Skip to main content
When someone sends an SMS message to your phone number that is connected to Hypersender, Hypersender will forward the message to your specified webhook URL. This allows you to receive SMS messages from your customers and respond to them programmatically.

​
How it works

1

A contact replies to your number

The message is received on the Android device that runs the Hypersender app.
2

Hypersender forwards it

The app reports the message to the API, which delivers it to the webhook URL configured for your instance.
3

Your application handles the reply

Your endpoint decides whether to answer automatically, store the conversation, or notify a human.

​
Configure the webhook

Set the webhook URL for your instance in the dashboard. Every inbound SMS arrives as a message-received event:

Message Received event

Payload reference for inbound SMS webhook events.
The endpoint must be publicly reachable over HTTPS and should return a 2xx response quickly. If your handler needs more time, queue the payload and return immediately, then process it in the background.

​
Reply to a received message

Send your answer to the same number that appears in the webhook payload:

Send Message

Send a reply using the number from the incoming payload.

​
Things to keep in mind

  • Replies are sent from your own SIM card number. Recipients never see a custom sender name.
  • Store the identifiers from the payload so you can rebuild conversations later — see Message Threads.
  • Keep the Android device powered and online. If it stops sending heartbeats for more than two hours, Hypersender marks it offline and inbound messages stop arriving — see the SMS Heartbeats Guide.
  • Honour opt-out requests in your own application logic.

​
Next steps

SMS webhooks overview

All SMS webhook events and how to configure them.

Threads in Laravel

List, edit, and delete message threads from the SDK.
Last modified on October 16, 2026