🔔 Push Notification Tester

Send real push notifications via Firebase Cloud Messaging (FCM), OneSignal API, or test browser notifications locally. 100% client-side and secure.

🌐 Browser Notification

⏳Checking permission...

📋 Response

Click "Send Browser Notification" to test...

🔥 Firebase Cloud Messaging

🔑 FCM Credentials
Find in Firebase Console → Project Settings → Cloud Messaging
FCM registration token or topic name (e.g., /topics/news)

📋 API Response

Enter your FCM credentials and click "Send FCM Notification" to test...

📱 OneSignal Push

🔑 OneSignal Credentials
Find in OneSignal Dashboard → Settings → Keys & IDs
Keep this key secure!

📋 API Response

Enter your OneSignal credentials and click "Send OneSignal Notification" to test...

Tool Features

  • Multi-Platform: Test FCM, OneSignal, and native browser Web Push.
  • 100% Client-Side: Your API keys never touch our servers.
  • Instant Debugging: See API responses in real-time.
  • No Signup: Use immediately without any registration.

Security & Privacy

All API calls are made directly from your browser to the FCM/OneSignal endpoints. We do not log, store, or process your credentials. You can verify this by opening your browser's DevTools and inspecting network requests.

Related Developer Tools

JSON Formatter HTTP Headers CORS Checker

❓ Frequently Asked Questions

How do I test FCM push notifications?+
You need your Server Key (from Firebase Console > Project Settings > Cloud Messaging) and a device token or topic. Enter these and your message content, then click send. The API response will tell you if the notification was delivered.
Is my FCM Server Key secure using this tool?+
Yes. This tool runs 100% in your browser. Your API keys are never stored on our servers. They are sent directly to the FCM or OneSignal API endpoints from your browser.
What is the difference between FCM v1 and Legacy API?+
FCM Legacy API uses a simple Server Key for authentication. FCM HTTP v1 requires OAuth 2.0 tokens from a Service Account, which needs server-side processing due to browser CORS limitations. This tool currently supports the Legacy API.
How do I find my OneSignal Player ID?+
The Player ID is assigned to each subscribed device. You can find it in your OneSignal Dashboard under Audience > All Users, or via your app's SDK callback when the user subscribes.
Why isn't my browser notification showing?+
Check if notification permission is 'Granted' in your browser. If it's denied, you'll need to reset permissions in your browser settings. Also, some browsers suppress notifications if you have 'Focus Assist' or 'Do Not Disturb' mode enabled.