Skip to main content


This Web3Inbox SDK provides you the building blocks necessary to allow users to subscribe, receive notifications, and manage notification preferences, all from your app's UI. The Web3Inbox SDK supports both React hooks and JavaScript-based integrations.

Before begin using Web3Inbox, you will first need to setup your project to send notifications.


npm i @web3inbox/core @web3inbox/react

Example Usage

This basic example demonstrates how to use the Web3Inbox SDK to subscribe to notifications and receive them in your app. Refer to the API Reference for more details on the available methods.

Below is an example of adding the Web3Inbox SDK to a React project with wagmi. Wagmi is not required to use the Web3Inbox React hooks.

We have separated it so the initialization can be done executed once in the app, and the hooks can be used anywhere in the app.

import { initWeb3InboxClient } from "@web3inbox/react";

// The project ID and domain you setup in the Domain Setup section
const projectId = process.env.NEXT_PUBLIC_PROJECT_ID!;
const appDomain = process.env.NEXT_PUBLIC_APP_DOMAIN!;

domain: appDomain,
allApps: process.env.NODE_ENV !== "production",

// Index.tsx
import {
} from '@web3inbox/react'
import { useCallback, useEffect } from 'react'
import { useSignMessage, useAccount } from 'wagmi'

import Notifications from './Notifications'

export default function App() {
// Wagmi Hooks
const { address } = useAccount()
const { signMessageAsync } = useSignMessage()

// W3I Hooks
const { prepareRegistration } = usePrepareRegistration()
const { register, isLoading: isRegistering } = useRegister()
const { data: w3iClient, isLoading: w3iClientIsLoading } = useWeb3InboxClient()
const { isRegistered } = useWeb3InboxAccount(`eip155:1:${address}`)

// Registration of your address to allow notifications
// This is done via a signature of a message (SIWE) and the
// signMessageAsync function from wagmi
const handleRegistration = async () => {
try {
const { message, registerParams } = await prepareRegistration()
const signature = await signMessageAsync({ message: message })
await register({ registerParams, signature })
} catch (registerIdentityError: any) {

// Subscription to dapp notifications
// Subscribe can be called as a function post registration
// Can be moved above but shown for example clarity
const { subscribe, isLoading: isSubscribing } = useSubscribe()
const { unsubscribe, isLoading: isUnsubscribing } = useUnsubscribe()
const { data: subscription } = useSubscription()
const isSubscribed = Boolean(subscription)

// Note: We are using Web3Modal for the dapp <> wallet connection.
// The <w3m-button /> module is from Web3Modal. Check Web3Modal Docs for further info.
return (
<main className={styles.main}>
{w3iClientIsLoading ? (
<div>Loading W3I Client</div>
) : (
<h1>W3I QuickStart</h1>
<w3m-button />
<div className={styles.flexColumn}>
<button onClick={handleRegistration} disabled={isRegistered}>
{isRegistered ? 'Registered' : 'Register'}
onClick={isSubscribed ? unsubscribe : subscribe}
disabled={isSubscribing || isUnsubscribing}
{isSubscribed ? 'Unsubscribe' : 'Subscribe'}
<hr />
{isSubscribed ? <Notifications /> : null}
// Notifications.tsx
import { useNotifications } from '@web3inbox/react'
import React from 'react'
import styles from '@/styles/Notifications.module.css'

function Notifications() {
const { data: subscription } = useSubscription()
const { data: notifications } = useNotifications(5)

return (
<h2 className={styles.heading}>Notifications</h2>
<p>You have {subscription.unreadCount} unread notifications.</p>
<div className={styles.notificationsContainer}>
{!notifications?.length ? (
<p className={styles.fallbackText}>No notifications yet.</p>
) : ({ id, ...message }) => (
<div key={id} className={styles.message}>
<p>{message.isRead ? "Read" : "Unread"}</p>
<button onClick={message.markAsRead}>Mark as read</button>
<button onClick={nextPage}>Next page</button>

export default Notifications

UX Guidelines

For the best user experience we have several recommendations on how to build the Web3Inbox flows into your app:

  • Have an explicit opt-in UI to subscribe to notifications. Some users may not want to receive notifications, and enabling notifications requires the user to sign a message with their blockchain account. Enabling notifications should be optional, and if they do enable them they should be told that they will need to sign a message to enable this.
  • Have a button to unsubscribe from notifications once they are enabled. Users may want to stop receiving notifications, so you should have a button to unsubscribe from notifications if the user wants to.
  • Make use of notification types. These allow the user fine-grained control over what types of notifications they want to receive from your app. These allow users to only unsubscribe from the specific notifications they are no longer interested in, rather than needing to unsubscribe from your entire app. Your app should include functionality to manage notification preferences.