Skip to main content
POST
Inbound SMS webhooks send customer replies, keyword messages, and opt-outs to your endpoint.
Inbound SMS webhooks work regardless of send API version. You can receive replies and opt-outs for messages sent through the OAuth API or legacy APIs.

​
Quick facts

Body

application/x-www-form-urlencoded
​
SMS-Type
enum<string>
default:AuthCode
required

Message type.

Available options:
AuthCode,
Text
​
SMS-Content
string
default:Test reply
required

Full inbound SMS message body.

​
SMS-Keyphrase
string
default:*
required

First word of the message, used for keyword routing.

​
SMS-From
string
default:353861234567
required

Sender mobile number in Irish international format.

​
SMS-To
string
default:353871234568
required

Number the message was sent to. Opt-out payloads use shared shortcode 50123.

​
SMS-NotifyId
string
default:""
required

The notifyId from the original outbound message when available.

​
SMS-Verify
string
default:5b49b61a65520226f3da14764f7c182b
required

MD5 verification hash built from SMS-From + SMS-Content + your Client Secret.

​
SMS-TimeStamp
string
default:2026-04-09 16:03:11
required

Gateway receipt time, formatted as yyyy-MM-dd HH:mm:ss.

Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2} [0-9]{2}:[0-9]{2}:[0-9]{2}$
​
SMS-Network
string
default:""

Network code in MCC/MNC format. This field may be empty.

​
SMS-AuthCode
string
default:AUTH:reply/1450707

Legacy routing code used by older integrations. Ignore in new builds.

​
SMS-GroupCode
string
default:AUTH:G353871234568/*

Legacy group routing code used by older integrations. Ignore in new builds.

Response

200

Your webhook endpoint accepted the inbound SMS payload.

Last modified on July 14, 2026