Documentation
Build with Notirabbit.
Connect your website or app, ask for permission and send your first notification. Start with the SDK for your platform.
On this page
Choose your SDK
Use the integration that matches your project. One Notirabbit app can connect more than one platform.
Web SDK
JavaScriptConnect your website with a script and service worker.
Start setupExpo SDK
React Native · iOS & AndroidAdd native push to your Expo app with one package.
Start setupiOS SDK
Swift · Swift Package ManagerIntegrate APNs, rich notifications and taps in your native iOS app.
Start setupAndroid SDK
Kotlin · Native AndroidConnect your native Android app with FCM, notification images and tap handling.
Start setupFrom setup to your first notification
- Configure your appIn the dashboard, open your app and configure the platforms you use. Match the website domain, Android package or iOS bundle ID to your project.
- Connect an SDKCopy the public app key from App Settings → Keys & IDs and follow your SDK’s guide. Mobile SDKs include the Notirabbit service URLs.
- Test on your own deviceGrant notification permission, find the subscription in the dashboard and send a selected-device test. Check delivery and the notification’s destination.
Send from your backend
The SDK registers devices and reports engagement. Use the dashboard for manual messages or the Sending API to connect your backend, CMS or publishing workflow.
Explore the Sending APISending to mobile? Include platforms in your API request, such as ["ios", "android"]. Requests that omit it target Web only. See platform targeting.
The right key in the right place
| Credential | Where it belongs |
|---|---|
| Public app key | Your website or mobile SDK configuration. Get it from App Settings → Keys & IDs. |
| App secret | Your backend’s X-App-Secret header when calling the Sending API. |
| APNs key / FCM service account | Your app’s platform credentials in the dashboard. Never include these credentials in a client build. |