Credentials, encrypted
Upload your Firebase service account and APNs .p8 key once. Both are encrypted at rest with AES-256-GCM and never returned by any API.
Mobile push · FCM + APNs
One campaign. Every device.
Android via Firebase Cloud Messaging, iOS via Apple Push Notification service — both wired into the same campaigns, segments, and analytics as your web push. Upload your credentials once and stop maintaining two pipelines.
Per-channel overrides
Shared content with channel-specific tweaks: Android notification channels and collapse keys, iOS interruption levels, sounds, and thread IDs.
Transactional API
Order updates, payment alerts, OTP-adjacent flows — one REST call targets any user by your own user ID, on whichever device they used last.
Token health, automated
Expired and uninstalled tokens are detected on every send, marked dead, and swept on your schedule — your delivery rate stays honest.
iOS via FCM or direct
Route iOS through Firebase if that’s your stack, or talk to APNs directly with your .p8 key — both are first-class paths.
Same rules everywhere
Frequency caps, quiet hours, and preference-center opt-outs apply across web and mobile — one policy, every channel.
Built for apps that already exist.
You don’t need to swap SDKs or re-architect notifications. Keep collecting FCM/APNs tokens exactly as you do today, register them with one REST call, and ReachBell takes over segmenting, scheduling, retries, and analytics.
- Register device tokens with a single POST /subscribers call
- Native REST docs for Android (Kotlin), iOS (Swift), and React Native
- Deterministic A/B variants — the same user always sees the same variant
- Delivery receipts and click tracking per platform
- Sandbox APNs supported for TestFlight and debug builds
9:41
Order shipped 📦
Your order #4821 is on the way — arrives tomorrow.
Payment received
How it works
Live in an afternoon.
No SDK wrestling, no DevOps tickets — most teams finish setup before their chai goes cold.
Upload credentials
Drop in your Firebase service-account JSON and/or APNs .p8 key in Project Settings. Validated instantly, encrypted at rest.
Register tokens
Send each device token to POST /subscribers with tokenType fcm or apns — from your app or your backend.
Send everywhere
Campaigns target web and mobile subscribers together. Per-channel overrides apply automatically at delivery time.
FAQ
Questions, answered.
Everything teams usually ask before switching. Something missing? Email us — a human replies.
Do you support both FCM and APNs?
Yes. Android pushes go through Firebase Cloud Messaging (HTTP v1 API with your service account), and iOS pushes can go through FCM or directly to APNs using your .p8 token — whichever fits your setup.
Can I keep my existing push code in the app?
Yes. ReachBell works with the tokens your app already collects. You only add one API call to register each token — no SDK swap, no migration of your notification handling code.
How do transactional mobile pushes work?
Call POST /transactional/send with your own user ID (set via identify) and the message. ReachBell finds the user’s most recent device — web, Android, or iOS — and delivers within seconds, respecting your frequency caps.
What happens to tokens when users uninstall the app?
FCM and APNs report uninstalled or expired tokens on the next send. ReachBell marks them dead immediately, excludes them from future sends, and purges them after your configured retention window.