Notifications (Notify)
The Notify API lets you broadcast a single payload to many users across SMS, APNs (iOS push), FCM (Android push), and Facebook Messenger in one API call. Register each user's address once as a Binding, then call CreateNotification and Notify fans the message out per channel.
Pick Notify when you need to reach the same audience across multiple channels. For one‑off SMS, use Messaging directly.
Mental Model
Service ← namespace for bindings + credentials
└─ Credentials ← push certificates / FCM server keys
└─ Bindings ← one per user/device/channel (Address + BindingType)
└─ Notifications ← a single payload that fans out to bindingsA Binding is the link between a user identity (e.g. user_42) and a delivery target (an APNs token, FCM token, phone number, or Facebook PSID). One user can have many bindings — Notify will deliver across all of them.
The Notify Building Blocks
Service
Top‑level container that holds credentials and bindings. You'll typically have one Service per app environment.
Credential
Push certificates for APNs, FCM server keys, or other channel‑specific credentials. Upload once per Service.
Binding
The address book entry: maps an Identity to a delivery target (Address + BindingType).
Notification
Publish a payload — Notify resolves it against bindings and dispatches per channel.
Typical Flow
When to Use Each Channel
apn / fcm
For in‑app push notifications on iOS / Android. Best engagement when your app is installed.
sms
Fallback for users without your app, or for high‑urgency alerts that must reach the user.
facebook-messenger
Reach users who've opted into your Facebook Page's message channel.
Tags & Segments
Send to a group: tag bindings on creation, then publish a notification to a Tag instead of an Identity.