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
- Individual FCM registration-token addressing
- Optional sound and badge behavior configured per channel
- Deep-link + data payload passthrough
- Automatic OAuth token minting and caching
- Terminal invalid-token suppression
- Queued retries for transient FCM failures
Senddio Push vs. direct FCM
What changes once you ship Push on Senddio.
Push — FAQ
Connect your Firebase service account in Senddio. Firebase Cloud Messaging delivers to supported iOS, Android and web devices using registration tokens obtained by your application.
Set to to a single FCM registration token. Topic and condition addressing are not part of the current public /v1/send contract.
Yes, as channel configuration. The send request itself accepts title, body, optional string data and an FCM registration token; it does not accept a platform_overrides field.
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.