Inbound callbacks - Beem API

When you send a session message with a callback_url, Beem POSTs inbound user replies to that URL. This is separate from template delivery reports, which track WhatsApp template message status.

Callback flow

You send session message (with callback_url)
        │
        ▼
User replies on WhatsApp / Facebook / etc.
        │
        ▼
Beem POSTs JSON to your callback_url
        │
        ▼
Your server responds HTTP 200

Callback payload fields

Field	Description
`from`	User address (sender)
`to`	Your channel number
`channel`	Channel type (e.g. `whatsapp`)
`transaction_id`	Reference from your outbound message, if provided
`user_name`	Display name when available
`message_type`	`text`, `image`, `document`, `video`, `location`, `audio`, `contact`, `quick_reply`, `list`
`text`	Text body when `message_type` is `text`
`image`, `video`, `document`, `location`, `audio`	Media objects when applicable
`contacts`	Contact cards when `message_type` is `contact`

Sample payloads

Text reply
Image reply
Quick reply

{
  "from": "255701000001",
  "to": "255701000000",
  "channel": "whatsapp",
  "user_name": "James",
  "transaction_id": "12345",
  "message_type": "text",
  "text": "Yes, I'd like more info"
}

{
  "from": "255701000001",
  "to": "255701000000",
  "channel": "whatsapp",
  "user_name": "James",
  "transaction_id": "12345",
  "message_type": "image",
  "image": {
    "mime_type": "image/jpeg",
    "url": "https://www.example.com/photo.jpeg"
  }
}

{
  "from": "255701000001",
  "to": "255701000000",
  "channel": "whatsapp",
  "user_name": "James",
  "message_type": "quick_reply",
  "text": "Account Balance"
}

Your server requirements

Expose a public HTTPS endpoint.
Accept POST with Content-Type: application/json.
Return HTTP 200 to acknowledge receipt.

See the Receive a message API reference for the full webhook schema.