Inbound Message Payload

WEBHOOKInbound V2 · Smobi → Your Server

Inbound events contain customer replies and interactions. Inspect channel and the message subtype before reading the SMS or RCS content.

Smobi sends these payloads to your configured HTTPS receiver. These are outbound events, not callable endpoints on api.smobi.com. Configure Webhooks.

Payload Fields

application/json

smobiMessageIdstringrequired

The reference number of the message in the Smobi system

tostringrequired

The phone number of the recipient

fromstringrequired

The phone number of the sender

channelstringrequired

The channel of the message - indicates which payload field to access

Allowed values"SMS""RCS"

timestampstringrequired

The timestamp of the message

smsobject

SMS message content (present when channel is SMS)

Show child fieldsHide child fields

contentstring

Text content of the message

downloadUrlstring

Download URL of media content

fileExtensionstring

File extension of the media content

rcsmultiple types

RCS message content (present when channel is RCS)

Show child fieldsHide child fields

Variant

Use one of these shapes.

typestringrequired

Type of message content

Allowed values"TEXT"

contentstringrequired

Text content

Receiver Requirements

Validate the authentication headers configured for your receiver.
Persist or enqueue each accepted event before returning a successful 2xx response.
Handle repeated events and out-of-order status updates.

Example Payload

Payload JSON

{
  "smobiMessageId": "123e4567-e89b-12d3-a456-426614174000",
  "to": "15552223333",
  "from": "15551234567",
  "channel": "SMS",
  "timestamp": "2021-01-01T00:00:00.000Z",
  "sms": {
    "content": "Hello, world!"
  }
}

Example JSON sent by Smobi to your receiver.