What is Notification Api Tester
The Notification API Tester requests permission to send desktop or mobile notifications and displays the resulting permission state. Web notifications allow web applications to show system-level alerts even when the tab is not focused — useful for chat apps, email clients, build monitors, and calendar reminders. The tool calls Notification.requestPermission() on button click (which must happen inside a user gesture to comply with browser policies) and reports whether the permission was granted, denied, or dismissed. This is the first step in any notification integration — if permission is denied, no notification code will work regardless of implementation quality.
How to Use Notification Api Tester
- Step 1: Navigate to the Notification API Tester page. The page shows a test button and output area.
- Step 2: Click the **Test API** button. The browser displays a permission dialog asking whether to allow notifications from this site.
- Step 3: Choose Allow, Deny, or dismiss the dialog. The output area reports the resulting permission state: 'granted', 'denied', or 'default' (dismissed).
- Step 4: If the Notification API is not available (insecure context, unsupported browser), the output indicates the API is not supported.
- Step 5: The tool does not send a test notification — it only checks the permission state. Sending notifications requires additional code.
Why Use Notification Api Tester
Before integrating notifications into a web application, developers need to understand the permission flow and confirm their browser environment supports it. The Notification API Tester isolates the permission request into a single click, letting you test the dialog behavior without building notification infrastructure. This is especially valuable for understanding browser-specific differences — Chrome shows a lightweight permission prompt, while Safari requires the page to be a registered web app. QA teams use it to verify that permission states are correctly handled in the application's onboarding flow.
Privacy & Security
This tool runs entirely in your browser — no data ever leaves your device. There is no server round-trip, no upload, no logging, and no account required. Your input is processed locally using client-side JavaScript and is never stored, transmitted, or accessible to anyone else. When you close the tab, everything disappears.
Frequently Asked Questions
Why does the browser block the notification permission request?
<p>Browsers require that Notification.requestPermission() be called from a user gesture (click, tap, or keypress). If called from a script that runs on page load or from a timer, the browser may block or ignore the request. The tool calls it from a button click to comply with this requirement.</p>
Can I test notification content with this tool?
<p>The current version only tests permission state. To test actual notification content, you would need to extend the tool to call new Notification('title', { body: 'message' }) after permission is granted.</p>
What happens if I deny permission?
<p>If you click Deny, the permission state is set to 'denied' and the site cannot send notifications until the user manually resets the permission in the browser's site settings. This is a one-way operation — the site cannot re-request permission after denial.</p>