​

Messenger

​

Send a message

curl -X POST https://api.orbit.devotel.io/api/v1/messages/messenger \
  -H "X-API-Key: dv_live_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "to": "<recipient_psid>",
    "messaging_type": "RESPONSE",
    "message": {
      "text": "Hi! Thanks for messaging us."
    }
  }'

​

Response

{
  "data": {
    "id": "msg_msgr_abc123",
    "status": "queued",
    "channel": "messenger"
  },
  "meta": {
    "request_id": "req_xyz789",
    "timestamp": "2026-05-09T00:00:00Z"
  }
}

​

Capabilities

• Text, media, files — text, image, video, audio, generic file attachments.
• Buttons — postback, web_url, and phone_number button types via the structured-message body.
• Generic templates — single + multi-card carousels with title, subtitle, image, and up to 3 buttons per card.
• One-time notifications (OTN) — request and consume OTN tokens for a single follow-up outside the 24-hour window.
• Persistent menu + greeting text — configured directly through Meta’s Graph API against your connected Page. Orbit does not manage these from the dashboard.
• Webhook events — message.received fires for inbound text and attachment messages; message.sent, message.delivered, message.read, and message.failed cover the outbound lifecycle. Postbacks and referrals (button taps, m.me links, ad clicks) are received and processed by Orbit but are not currently dispatched to your webhook, so do not build automations that expect a message.received event for them. Opt-in plugin events update the recipient’s consent record server-side rather than firing a webhook. Messenger reports delivery status to Orbit using the same status mapping as WhatsApp: message.sent fires when Meta accepts the outbound message, message.delivered fires when Meta confirms the message reached the recipient’s device, and message.read fires when the recipient opens the conversation. Delivery receipts are relayed on this channel, so message.delivered can and does fire — you can use it as your delivery signal rather than treating message.sent (acceptance only) as confirmation. message.failed reflects a delivery failure reported by Meta; inspect the accompanying error code and treat it as a genuine send failure.

​

Onboarding flow

1. From the dashboard, navigate to Channels → Messenger.
2. Click Connect Page. Meta’s OAuth dialog requests pages_messaging and pages_show_list.
3. Select the Page(s) you want to attach. Orbit subscribes the Page to webhooks automatically.
4. (Optional) Add sender personas from Settings → Channels → Messenger to reply as named agent identities (for example, “Sarah, Sales”) on the same Page. Persistent menu and greeting text are configured directly through Meta’s Graph API — Orbit does not manage them from the dashboard.

​

Messaging windows

​

Common errors

​

Pricing