Receiving Messages
Inbound SMS & email
You don’t set up a carrier webhook — MOST does
Unlike raw Twilio/Telnyx, you never configure a provider webhook for inbound SMS. When MOST provisions your number, it automatically points the carrier’s inbound webhook at MOST (the Telnyx messaging profile’s webhook_url is set to MOST’s handler). Every text sent to your number is captured for you — no setup, no endpoint to maintain.
Where inbound lands
- Inbound SMS & DMs appear in your Communications inbox in the dashboard, recorded against the matching contact.
- Inbound email to your brand address (
hello@yourdomain) is received and forwarded to the account owner, and stored in your inbox.
Get inbound delivered to your webhook
To receive incoming messages in your own system, add a webhook in Settings → General → Webhooks. Every inbound message is then POSTed to your URL as a signed JSON event. The full event list, signing and retry rules are in Webhook events.
Events
message.received— an inbound SMSemail.received— an inbound email to your brand addresstest.ping— sent by the “Send test” button
Payload
POST https://your-app.com/webhooks/most
Content-Type: application/json
X-Most-Event: message.received
X-Most-Delivery: 6f1e… # unique per delivery
X-Most-Timestamp: 1782942000
X-Most-Signature-256: t=1782942000,v1=5c1d… # HMAC-SHA256("<t>.<body>", secret), hex
X-Most-Signature: 9a3b… # legacy: HMAC-SHA256(body, secret), hex
{
"id": "6f1e…",
"event": "message.received",
"created_at": "2026-07-01T21:40:00.000Z",
"data": {
"channel": "sms",
"from": "+15551234567",
"to": "+15557654321",
"body": "Do you have this in size M?",
"contact_id": "c1a2b3c4-…",
"provider": "telnyx"
}
}Verify the signature
Use X-Most-Signature-256: compute HMAC-SHA256 of "<t>.<raw body>" with your endpoint’s signing secret, compare it (constant-time) to v1, and reject a t more than 5 minutes from now so a captured request can’t be replayed. Full example on Webhook events. The older X-Most-Signature (HMAC of the body alone) is still sent, unchanged.
Respond with a 2xx to acknowledge. A 5xx, 408, 429 or timeout is retried for about a day (8 retries); any other 4xx is not retried. An endpoint that keeps failing is auto-disabled and can be re-enabled in Settings.
Or react inside MOST
Prefer not to run your own server? Build a workflow to auto-reply, tag, or start a sequence on inbound activity — see workflow webhooks.