--- title: Notification slug: Web/API/notification tags: - API - Interface - NeedsTranslation - Notifications - Reference - TopicStub translation_of: Web/API/Notification ---
The Notification interface of the Notifications API is used to configure and display desktop notifications to the user. These notifications' appearance and specific functionality vary across platforms but generally they provide a way to asynchronously provide information to the user.
Notification object.These properties are available only on the Notification object itself.
denied — The user refuses to have notifications displayed.granted — The user accepts having notifications displayed.default — The user choice is unknown and therefore the browser will act as if the value were denied.These properties are available only on instances of the Notification object.
options parameter.options parameter.options parameter.options parameter.options parameter.options parameter.options parameter.These methods are available only on the Notification object itself.
These properties are available only on an instance of the Notification object or through its prototype. The Notification object also inherits from the {{domxref("EventTarget")}} interface.
Assume this basic HTML:
<button onclick="notifyMe()">Notify me!</button>
It's possible to send a notification as follows — here we present a fairly verbose and complete set of code you could use if you wanted to first check whether notifications are supported, then check if permission has been granted for the current origin to send notifications, then request permission if required, before then sending a notification.
function notifyMe() {
// Let's check if the browser supports notifications
if (!("Notification" in window)) {
alert("This browser does not support desktop notification");
}
// Let's check whether notification permissions have already been granted
else if (Notification.permission === "granted") {
// If it's okay let's create a notification
var notification = new Notification("Hi there!");
}
// Otherwise, we need to ask the user for permission
else if (Notification.permission !== "denied") {
Notification.requestPermission().then(function (permission) {
// If the user accepts, let's create a notification
if (permission === "granted") {
var notification = new Notification("Hi there!");
}
});
}
// At last, if the user has denied notifications, and you
// want to be respectful there is no need to bother them any more.
}
{{EmbedLiveSample('Example', '100%', 30)}}
In many cases, you don't need to be this verbose. For example, in our Emogotchi demo (see source code), we simply run {{domxref("Notification.requestPermission")}} regardless to make sure we can get permission to send notifications (this uses the newer promise-based method syntax):
Notification.requestPermission().then(function(result) {
console.log(result);
});
Then we run a simple spawnNotification() function when we want to fire a notification — this is passed arguments to specify the body, icon, and title we want. Then it creates the necessary options object and fires the notification using the {{domxref("Notification.Notification","Notification()")}} constructor.
function spawnNotification(body, icon, title) {
var options = {
body: body,
icon: icon
};
var n = new Notification(title, options);
}
| Specification | Status | Comment |
|---|---|---|
| {{SpecName('Web Notifications')}} | {{Spec2('Web Notifications')}} | Living standard |
{{Compat("api.Notification")}}