Direct to APNs & FCM
HTTP/2 to Apple and FCM HTTP v1 to Google using your own keys. No third-party dependency, low latency.
Push infrastructure for mobile apps
Send push notifications straight through APNs and Firebase Cloud Messaging, with no middleman. OneSignal-compatible API, SDKs for Flutter, React Native, Swift, Kotlin and .NET MAUI.
Fully supported
Features
From device registration and audience targeting to delivery tracking – all in one dashboard.
HTTP/2 to Apple and FCM HTTP v1 to Google using your own keys. No third-party dependency, low latency.
Same POST /notifications format. A backend already on OneSignal only needs a new API address and key.
Send to everyone, by user (External ID), by tag, by device or by token. See the estimated audience before sending.
Show the CallKit call screen on iPhone and a ringing screen on Android, even when the app is closed.
Track successful and failed deliveries with sample errors from Apple/Google. Dead tokens are removed automatically.
APNs/FCM keys are encrypted and API keys are stored hashed. Go on-premise to keep data inside your own systems.
Quick start
Get an App ID for your app and an API Key for your backend. One project per app.
Upload your Apple .p8 key and Firebase service account JSON. The βTestβ button verifies the setup instantly.
Install the SDK, call one function to register the device, then send from the dashboard or the REST API.
Use cases
Order status updates, abandoned carts, flash sales and personalised coupons.
Balance changes, transaction codes and login alerts – sent at high priority, with data on your own infrastructure.
New messages and incoming calls that ring like a regular phone call on both iOS and Android.
Real-time trip updates for customers and drivers, targeted per user.
Class reminders, grade alerts and school news to parents by class or grade using tags.
Approvals and ERP/CRM alerts for employees. Install on-premise inside your network.
Free
Every feature included: unlimited projects, devices and notifications, plus VoIP calls and OneSignal sync. No credit card required.
FAQ
A push notification is a message that appears on a phone's screen even when the app is not open. On iOS it is delivered through the Apple Push Notification service (APNs); on Android through Firebase Cloud Messaging (FCM).
TingPush sends directly to APNs and FCM with your own credentials, with no middleman. The send API uses the same request format as OneSignal, so your backend only needs a new API address and key. You can also install TingPush on your own servers so all device data stays in your systems.
No. The OneSignal Sync feature imports all devices (with External ID and tags) from your OneSignal account into TingPush, and can keep syncing on a schedule during the migration. Your users don't need to update the app right away.
iOS (APNs, including VoIP push for CallKit) and Android (FCM HTTP v1). SDKs are available for Swift, Kotlin, Flutter, React Native and .NET MAUI.
Yes. TingPush sends VoIP pushes on iOS to show the CallKit screen and high-priority data messages on Android to show a ringing screen, even when the app is closed.
For iOS: a .p8 key file, Team ID, Key ID and Bundle ID from Apple Developer. For Android: a service account JSON file from the Firebase Console. The setup page walks you through each step with screenshots.