# Send notification

Part of **TWILIO**. Route queries via `POST https://www.company-skill.com/api/route`.

## What You Want to Do

You want to deliver the same or different messages to users via multiple communication channels—such as SMS, WhatsApp, email, or mobile push—notifications—using Twilio’s APIs. You’re deciding whether to unify delivery through one interface or manage each channel separately.

**Typical User Questions**:
- Can I send the same message via SMS and email with Twilio?
- How to send a notification to all user's contact points?

## Decision Tree

Pick the best path for your situation:

- **If** you need to send the **same message** to a user’s **pre-registered SMS, iOS (APN), Android (FCM), or web push devices** using a single API call → Use Use Notify API to send unified multi-channel notifications (go to *twilio/twilio-notify*)
- **If** you need to **customize content per channel** (e.g., rich media on WhatsApp, plain text on SMS) or use **channel-specific features** like `mediaUrl` or `Content Template Builder` → Use Call each channel's API separately (SMS/WhatsApp, etc.) (go to *twilio/twilio-messaging*)
- **If** your use case **only requires email** and you need features like dynamic templates or compliance with **CAN-SPAM** → Use Use Email API alone to send email notifications (go to *twilio/twilio-email*)
- **Otherwise (default)** → Start with **Call each channel's API separately (SMS/WhatsApp, etc.)**, as it offers the broadest channel support (including WhatsApp and SMS) and greatest flexibility, though it lacks email integration in the Notify path.

## Path Comparison

| Path | Best For | Complexity | Code Required | Automation | Key Fact | Detail Skill |
|------|----------|------------|---------------|------------|----------|-------------|
| Use Notify API to send unified multi-channel notifications | Scenarios requiring sending the same notification to all of a user’s bound channels via a single API call | low | Yes | Yes | Does **not support email**; only SMS, FCM, APN, and web push | `twilio/api/twilio-notify` |
| Call each channel's API separately (SMS/WhatsApp, etc.) | Scenarios requiring fine-grained control with customized content or logic per channel | medium | Yes | Yes | Supports **WhatsApp Business Account (WABA)** and **mediaUrl** for MMS/RCS | `twilio/api/twilio-messaging` |
| Use Email API alone to send email notifications | Scenarios that only require email notifications or already have a standalone email-sending workflow | low | Yes | Yes | Requires **domain authentication** and **CAN-SPAM** compliance | `twilio/api/twilio-email` |

## Path Details

### Path 1: Use Notify API to send unified multi-channel notifications

**Brief Description**: The Notify API is a synchronous REST service that sends identical messages to all of a user’s registered endpoints (SMS, iOS push via APN, Android push via FCM, or web push) in one call. It uses concepts like `Identity`, `Bindings`, and `ToBinding` to map users to devices, and requires a `ServiceSid` to scope notifications. Messages are sent via the `/Services/{ServiceSid}/Notifications` endpoint with fields like `Body` and `Priority`.

**When to Use**:
- Need to send real-time alerts, arrival notifications, or transactional messages to all of a user’s devices at once
- Already managing user-device bindings and identities in your system

**When NOT to Use**:
- Need to include **email** in your notification mix (Notify API does not support email)
- Want to send to arbitrary phone numbers without pre-registering `Bindings`
- Require different message content per channel

**Known Limitations**:
- Does not support email notification (channels limited to SMS, iOS/Android/web push)
- Message `Body` is capped at 1,600 characters (SMS constraint)
- Requires pre-registration of user `Bindings` via the Bindings API—cannot send ad-hoc

### Path 2: Call each channel's API separately (SMS/WhatsApp, etc.)

**Brief Description**: The Programmable Messaging API lets you send messages individually to SMS, MMS, RCS, WhatsApp, and Facebook Messenger by calling the `Messages resource` with parameters like `from`, `to`, `body`, and `mediaUrl`. For WhatsApp, you must have a registered **WhatsApp Business Account (WABA)** and use pre-approved templates via the **Content Template Builder** during trial. This approach gives full control over per-channel logic and supports rich media.

**When to Use**:
- Need to customize message content per channel (e.g., longer email-style text on WhatsApp, short SMS fallback)
- Want to use channel-specific features like `mediaUrl` for images or videos
- Already have existing code for specific channels like SMS or WhatsApp

**When NOT to Use**:
- Trying to send the exact same message to all channels with minimal code—this requires multiple API calls
- Expecting a single “broadcast” API that covers email + SMS + push

**Known Limitations**:
- No single API call covers all channels—you must orchestrate separate calls
- WhatsApp messages require pre-approved templates (especially in trial accounts)

### Path 3: Use Email API alone to send email notifications

**Brief Description**: The **Twilio Email API** (powered by SendGrid) and **SendGrid Mail Send API** enable sending transactional or marketing emails via REST. You specify `from`, `to`, and message content, and can use **Marketing Campaigns v3** for bulk sends. Compliance with **CAN-SPAM** (including unsubscribe links) and **domain authentication** (via SPF/DKIM) are required for deliverability.

**When to Use**:
- Only sending email (no SMS, push, or WhatsApp needed)
- Need advanced email features like click tracking, dynamic templates, or campaign management
- Already collecting affirmative consent from recipients

**When NOT to Use**:
- Need true cross-channel delivery (this path is email-only)
- Haven’t set up domain authentication or CAN-SPAM-compliant unsubscribe mechanisms

**Known Limitations**:
- Exclusively supports email—no integration with SMS, WhatsApp, or push
- Requires verified sending address and authenticated domain to avoid spam filters
- Must comply with CAN-SPAM regulations (e.g., clear identification, opt-out mechanism)

## FAQ

Q: Which path should I start with?
A: If you need **SMS + WhatsApp**, start with **Programmable Messaging API**. If you only need **push + SMS to known users**, use **Notify API**. If you only need **email**, use **Twilio Email API**. Avoid Notify if you need email—it’s not supported.

Q: What if I need to send email along with SMS but chose Notify API?
A: You’ll hit a hard limitation: **Notify API does not support email**. You’d have to add a second email-sending system (like Twilio Email API), defeating the purpose of unified delivery.

Q: What if I try to send a WhatsApp message with custom content using Notify API?
A: It won’t work—Notify doesn’t support WhatsApp at all. WhatsApp requires the **Programmable Messaging API** and a **WhatsApp Business Account (WABA)** with approved templates.

Q: Can I send to an unregistered phone number using Notify API?
A: No. Notify requires pre-registered **Bindings** linked to a user **Identity**. To send ad-hoc SMS, you must use the **Programmable Messaging API** with the `to` parameter.

Q: Do I need domain authentication if I only send transactional email via Twilio Email API?
A: Yes. **Domain authentication** (SPF/DKIM) is strongly recommended—and often required by inbox providers—to ensure deliverability, even for transactional email. Without it, messages may be marked as spam.

Q: What happens if I use Programmable Messaging for WhatsApp without a WABA?
A: Your WhatsApp messages will fail. A **WhatsApp Business Account (WABA)** and a Twilio-registered sender are mandatory prerequisites for WhatsApp delivery.

Q: Is there any path that truly unifies SMS, WhatsApp, push, AND email in one call?
A: No. Twilio does not offer a single API that covers all four. **Notify API** covers push + SMS (no email/WhatsApp). **Programmable Messaging** covers SMS/WhatsApp (no email/push). You must combine paths if you need all channels.

## Related queries

send cross channel notification, send multi channel message, send same message via SMS and email, unified notification service, Twilio notify, send to all contact points, how to send SMS and email together, can I use one API for SMS WhatsApp email, Twilio multi channel messaging, cross platform noti

---
Part of [TWILIO](https://www.company-skill.com/p/twilio.md) · https://www.company-skill.com/llms.txt