Production-ready push, on day one.
The boring infrastructure — signing, retries, suppressions, webhook verification, audit — is done. Your code is one POST.
- FCM-managed delivery to iOS, Android, Web
- Token, topic and condition addressing
- Per-platform overrides (APNs/FCM nuances abstracted)
- Deep-link + data payload passthrough
- Quiet-hours respect via channel preference chain
- Open + tap analytics via SDK callback
- Device-token registry with last-seen tracking
You're in good company on Push.
Composite quotes from interviews with current Senddio customers shipping push in production.
Senddio Push vs. direct FCM
What changes once you ship Push on Senddio.
Push — FAQ
Senddio uses Firebase Cloud Messaging to deliver push notifications to iOS (through Apple's push service), Android and the web. Senddio owns the service-account credentials, so you only need to register device tokens or topics.
Address the send to a topic by prefixing the recipient with "topic:" — for example, "topic:weekly-digest". Senddio fans the notification out to every device subscribed to that topic. You can also combine topics with conditions.
Yes. Use the platform_overrides block in your send request to set iOS fields like sound, badge, category and content-available, or Android fields like channel ID and priority. Senddio maps them to the underlying provider payload for you.
Yes. Give the agent its own key, restrict it to the push channel, and the agent can fire notifications through the same send tool. Every push is labelled with the agent name in your dashboard for clean auditing.
Yes. The free plan includes 100 push notifications a month so you can try the channel. Starter and Pro plans include production volumes.