SMS8

Forward SMS to a webhook every incoming text as signed JSON.

To forward SMS to a webhook with SMS8, open Webhooks in the dashboard, add your HTTPS URL and tick the incoming message events. Each text your paired Android phone receives is then sent to that URL as a JSON POST with an X-Signature HMAC-SHA256 header, and failed deliveries are retried for up to 30 days.

How to forward SMS to a webhook

A few minutes from a paired phone to your first event.

1

Pair your Android phone

Install the SMS8 app on an Android 7 or newer phone with a SIM and scan the pairing code from the dashboard.

2

Open Webhooks

In app.sms8.io, open the Webhooks page and click to add a webhook.

3

Enter the URL and secret

Paste your HTTPS endpoint, give it a name and keep the signing secret. Each webhook has its own secret, separate from your API key.

4

Choose the events

Tick received and messages for incoming texts (the payload carries "event": "messages"). Add delivered and failed if you also want delivery reports.

5

Text your number

Send a text to the SIM in your paired phone. The event shows in the webhook delivery log with its HTTP status.

What the webhook receives

SMS8 sends a POST with Content-Type: application/json. The body is an envelope with the event name, a timestamp, your user ID and a data list of the messages that arrived:

{
  "event": "messages",
  "timestamp": "2026-11-16T09:41:07+00:00",
  "userID": 1234,
  "data": [
    {
      "ID": 98765,
      "number": "+14155550100",
      "message": "Yes, Thursday at 3 works for me",
      "deviceID": 42,
      "simSlot": 0,
      "userID": 1234,
      "status": "Received",
      "sentDate": "2026-11-16T09:41:05+0000"
    }
  ],
  "frontFields": { "number": "+14155550100", "body": "Yes, Thursday at 3 works for me", "...": "..." }
}

The values above are an example. number is the sender, message the text, and deviceID and simSlot tell you which phone and SIM received it. frontFields repeats the first message in an older flat shape for integrations built before the envelope.

Verify the signature

Every request carries an X-Signature header in the form sha256= plus the HMAC-SHA256 of the raw body, made with that webhook's signing secret. Compute the same value and compare with a constant-time check:

$raw = file_get_contents('php://input');
$expected = 'sha256=' . hash_hmac('sha256', $raw, $signingSecret);
if (!hash_equals($expected, $_SERVER['HTTP_X_SIGNATURE'] ?? '')) {
    http_response_code(401);
    exit;
}
$event = json_decode($raw, true);
foreach ($event['data'] as $sms) {
    // $sms['number'], $sms['message'], $sms['deviceID'], $sms['simSlot']
}
http_response_code(200);

Retries and the delivery log

Return a 2xx status quickly. If SMS8 does not get one, it retries at 3 minutes, 5 minutes, 30 minutes, 1 hour, 6 hours, 1 day, 3 days, 7 days and 30 days. Every attempt is listed in the delivery log on the Webhooks page with its status code and response, so you can see what failed and when.

The same pattern in Python, Node.js, C# and curl is on the SMS API pages, and the full event list is in the SMS8 API documentation. If you are deciding between a webhook and a polling loop, read webhook vs polling for incoming SMS.

Events you can forward

Each webhook picks its own events, and you can add several webhooks for different services.

01

Incoming messages

A text arrived on one of your phones. The event most CRM, helpdesk and alert setups need.

02

Delivered

The recipient's carrier confirmed a message you sent.

03

Failed

A message you sent could not go out, for example a bad number or no signal.

04

USSD reply

The carrier answered a USSD code you sent from the phone.

05

Phone paired

A new phone joined your account.

Why choose SMS8 for SMS webhooks

Inbound SMS on a real number, without a number to rent.

01

Your own number

Texts arrive on the SIM in your own Android phone, the number your customers already text, and you can reply from it through the API.

02

Flat price, unlimited messages

USD 29 a month for 1 phone, USD 89 for 5 and USD 229 for 20, with unlimited SMS and MMS and no fee per message or per event.

03

No A2P 10DLC filing

Messages go person-to-person from your SIM, so there is no brand or campaign registration.

04

Signed and retried

Per-webhook secrets with an HMAC-SHA256 signature, retries for up to 30 days and a delivery log you can read.

05

API, MCP and integrations

REST API with an X-Api-Key header, the sms8-sdk npm package, an MCP server for AI agents and official Zapier and Make apps.

06

Setup in minutes

Pair a phone, add a URL and receive. 3-day trial with 30 messages, no card needed.

Common questions

Still unsure? We answer fast.

Pair an Android phone with SMS8, open Webhooks in the dashboard, add your HTTPS URL and tick the incoming message events. Each text the phone receives is posted to your URL as JSON within moments.

Each request has an X-Signature header: sha256= followed by the HMAC-SHA256 of the raw body, keyed with that webhook's signing secret. Recompute it on your server and reject any request where the two do not match.

SMS8 retries at increasing intervals, from 3 minutes up to 30 days, and logs every attempt with its status code on the Webhooks page.

Yes. Add more than one webhook, each with its own URL, secret and events, for example one for your CRM and one for an n8n workflow.

Yes. You can read messages with POST /api/v1/messages/read on a schedule. Webhooks are faster and lighter; the trade-offs are in our article on webhook vs polling for incoming SMS.

Get incoming texts on your server

Pair a phone, add a webhook URL and every SMS arrives as signed JSON. 3-day trial with 30 messages, no card needed.