LoopMessage review

LoopMessage positions itself as a messaging carrier rather than an iMessage tool — one API reaching iMessage, SMS, RCS and WhatsApp, choosing the cheapest channel that will actually reach a given person. If your customer base is genuinely mixed, or international, that routing is worth more than any single-protocol feature list.

What it is good at

• +WhatsApp alongside iMessage, RCS and SMS — the widest reach on this page.
• +Channel routing can cut cost by picking the cheapest path that still lands.
• +Expressive iMessage features supported: effects, tapbacks, audio messages.
• +Built for AI assistants as well as humans, so the webhook model suits automation.

Where it will bite you

• −Four channels means four sets of rules, limits and compliance regimes to learn.
• −More configuration up front than a single-channel API.
• −The expressive features are easy to overuse and read as spam.

The shape of the API

Illustrative — parameter names and endpoints change. Treat this as the flavour of the integration, and copy the real thing from the official docs.

curl -X POST https://server.loopmessage.com/api/v1/message/send/ \
  -H "Authorization: $LOOP_AUTH_KEY" \
  -H "Loop-Secret-Key: $LOOP_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "recipient": "+15551234567",
    "text": "Doors open at 7. Grab your spot: https://acme.co/rsvp?utm_source=imessage&utm_medium=sms&utm_campaign=launch_night",
    "effect": "confetti"
  }'

Tracking links with LoopMessage

Whatever you send with, build the URL from one helper so tagging is consistent across every job and campaign. Open the UTM builder to generate one now.