PushManager: unregister() method

Deprecated: This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.

Non-standard: This feature is non-standard and is not on a standards track. Do not use it on production sites facing the Web: it will not work for every user. There may also be large incompatibilities between implementations and the behavior may change in the future.

Note: This feature is available in Web Workers.

The unregister() method was used to ask the system to unregister and delete the specified endpoint.

Note: In the updated API, a subscription can be unregistered via the PushSubscription.unsubscribe() method.





A pushEndpoint to be unregistered.

Return value

A DOMRequest object to handle the success or failure of the method call.

If the method call is successful, the request's result will be a PushRegistration object representing the endpoint that has been unregistered.


Those objects are anonymous JavaScript objects with the following properties:


A string representing the URL of the unregistered endpoint.


Undefined when unregister.onsuccess is called.


const req = navigator.push.unregister(pushEndpoint);

req.onsuccess = (e) => {
  const endpoint = req.result;
  console.log(`Unregistered endpoint: ${endpoint}`);

req.onerror = (e) => {
  console.error(`Error unregistering the endpoint: ${e.error}`);


This feature is not part of any specification anymore. It is no longer on track to become a standard.

Browser compatibility

BCD tables only load in the browser

See also