---
title: "Get Push Notification Instance"
url: https://docs.catalyst.zoho.com/en/sdk/javascript/v1/cloudscale/push-notifications/get-instance/
description: "This page describes the method to perform operations in the DataStore component."
last_updated: 2026-09-09T10:45:38Z
service: CloudScale
type: general
related_links:
  - name: "Catalyst CloudScale"
    url: /en/cloud-scale/
  - name: "Push Notifications Help Documentation"
    url: /en/cloud-scale/help/push-notifications/introduction/
  - name: "Java SDK Documentation"
    url: /en/sdk/java/v1/cloud-scale/push-notifications/send-notifications/
  - name: "Python SDK Documentation"
    url: /en/sdk/python/v1/cloud-scale/push-notifications/get-component-instance/
  - name: "REST API Documentation"
    url: /en/api/code-reference/cloud-scale/push-notifications/web/send-web-push-notifications/#SendWebPushNotifications
repository:
  name: "Repository"
  url: https://github.com/catalystbyzoho/zcatalyst-sdk-js
---

# Get Push Notification Instance

> **Note:** Ensure you have installed the [required package](https://docs.catalyst.zoho.com/en/sdk/javascript/v1/cloudscale/push-notifications/overview/#prerequisites) to use this SDK method.

You can get the `pushNotification` component reference as shown below. This will not fire a server-side call. You will refer to this component instance in various code snippets when working with the Push Notification component.

```javascript
const pushNotification = new PushNotification(); // Get push notification instance
```

> **Note:**

- Passing an initialized app instance to a component determines the authentication scope it uses.
- To perform an operation with user-level permissions, initialize the SDK with User scope, or with custom credentials, and pass that instance to the component. This runs the operation in the user's scope or custom credential scope instead of the default admin scope.

```javascript
const pushNotification = new PushNotification(app);
```

- If your Function or AppSail application needs both custom credentials and admin authentication at the same time, give each initialization a unique app name, otherwise the custom initialization can overwrite your existing admin credentials.
- In all cases, explicitly pass the matching app instance to each component so it uses the intended authentication scope; if none is provided, the SDK defaults to the admin credentials.