How to use Notification Hubs from Java

This topic describes the key features of the new fully supported official Azure Notification Hub Java SDK. This project is an open-source project and you can view the entire SDK code at Java SDK.

In general, you can access all Notification Hubs features from a Java/PHP/Python/Ruby back-end using the Notification Hub REST interface as described in the MSDN topic Notification Hubs REST APIs. This Java SDK provides a thin wrapper over these REST interfaces in Java.

The SDK currently supports:

  • CRUD on Notification Hubs
  • CRUD on Registrations
  • Installation Management
  • Import/Export Registrations
  • Regular Sends
  • Scheduled Sends
  • Async operations via Java NIO
  • Supported platforms: APNS (iOS), FCM (Android), WNS (Windows Store apps), MPNS(Windows Phone), ADM (Amazon Kindle Fire), Baidu (Android without Google services)


Microsoft Push Notification Service (MPNS) has been deprecated and is no longer supported.

SDK Usage

Compile and build

Use Maven

To build:

mvn package


Notification Hub CRUDs

Create a NamespaceManager:

NamespaceManager namespaceManager = new NamespaceManager("connection string")

Create Notification Hub:

NotificationHubDescription hub = new NotificationHubDescription("hubname");
hub.setWindowsCredential(new WindowsCredential("sid","key"));
hub = namespaceManager.createNotificationHub(hub);


hub = new NotificationHub("connection string", "hubname");

Get Notification Hub:

hub = namespaceManager.getNotificationHub("hubname");

Update Notification Hub:

hub.setMpnsCredential(new MpnsCredential("mpnscert", "mpnskey"));
hub = namespaceManager.updateNotificationHub(hub);

Delete Notification Hub:


Registration CRUDs

Create a Notification Hub client:

hub = new NotificationHub("connection string", "hubname");

Create Windows registration:

WindowsRegistration reg = new WindowsRegistration(new URI(CHANNELURI));

Create iOS registration:

AppleRegistration reg = new AppleRegistration(DEVICETOKEN);

Similarly you can create registrations for Android (FCM), Windows Phone (MPNS), and Kindle Fire (ADM).

Create template registrations:

WindowsTemplateRegistration reg = new WindowsTemplateRegistration(new URI(CHANNELURI), WNSBODYTEMPLATE);
reg.getHeaders().put("X-WNS-Type", "wns/toast");

Create registrations using create registration ID + upsert pattern:

Removes duplicates due to any lost responses if storing registration IDs on the device:

String id = hub.createRegistrationId();
WindowsRegistration reg = new WindowsRegistration(id, new URI(CHANNELURI));

Update registrations:


Delete registrations:


Query registrations:

  • Get single registration:
  • Get all registrations in hub:
  • Get registrations with tag:
  • Get registrations by channel:

All collection queries support $top and continuation tokens.

Installation API usage

Installation API is an alternative mechanism for registration management. Instead of maintaining multiple registrations, which are not trivial and may be easily done incorrectly or inefficiently, it is now possible to use a SINGLE Installation object.

Installation contains everything you need: push channel (device token), tags, templates, secondary tiles (for WNS and APNS). You don't need to call the service to get ID anymore - just generate GUID or any other identifier, keep it on the device and send to your backend together with push channel (device token).

On the backend, you should only do a single call to CreateOrUpdateInstallation; it is fully idempotent, so feel free to retry if needed.

As example for Amazon Kindle Fire:

Installation installation = new Installation("installation-id", NotificationPlatform.Adm, "adm-push-channel");

If you want to update it:

installation.addTemplate("template1", new InstallationTemplate("{\"data\":{\"key1\":\"$(value1)\"}}","tag-for-template1"));
installation.addTemplate("template2", new InstallationTemplate("{\"data\":{\"key2\":\"$(value2)\"}}","tag-for-template2"));

For advanced scenarios, use the partial update capability, which allows to modify only particular properties of the installation object. Partial update is subset of JSON Patch operations you can run against Installation object.

PartialUpdateOperation addChannel = new PartialUpdateOperation(UpdateOperationType.Add, "/pushChannel", "adm-push-channel2");
PartialUpdateOperation addTag = new PartialUpdateOperation(UpdateOperationType.Add, "/tags", "bar");
PartialUpdateOperation replaceTemplate = new PartialUpdateOperation(UpdateOperationType.Replace, "/templates/template1", new InstallationTemplate("{\"data\":{\"key3\":\"$(value3)\"}}","tag-for-template1")).toJson());
hub.patchInstallation("installation-id", addChannel, addTag, replaceTemplate);

Delete Installation:


CreateOrUpdate, Patch, and Delete are eventually consistent with Get. Your requested operation just goes to the system queue during the call and is executed in background. Get is not designed for main runtime scenario but just for debug and troubleshooting purposes, it is tightly throttled by the service.

Send flow for Installations is the same as for Registrations. To target notification to the particular Installation - just use tag "InstallationId:{desired-id}". For this case, the code is:

Notification n = Notification.createWindowsNotification("WNS body");
hub.sendNotification(n, "InstallationId:{installation-id}");

For one of several templates:

Map<String, String> prop =  new HashMap<String, String>();
prop.put("value3", "some value");
Notification n = Notification.createTemplateNotification(prop);
hub.sendNotification(n, "InstallationId:{installation-id} && tag-for-template1");

Schedule Notifications (available for STANDARD Tier)

The same as regular send but with one additional parameter - scheduledTime, which says when notification should be delivered. Service accepts any point of time between now + 5 minutes and now + 7 days.

Schedule a Windows native notification:

Calendar c = Calendar.getInstance();
c.add(Calendar.DATE, 1);
Notification n = Notification.createWindowsNotification("WNS body");
hub.scheduleNotification(n, c.getTime());

Import/Export (available for STANDARD Tier)

You may need to perform bulk operation against registrations. Usually it is for integration with another system or a massive fix to update the tags. We don't recommend using the Get/Update flow if thousands of registrations are involved. The system's Import/Export capability is designed to cover the scenario. You'll provide access to a blob container under your storage account as a source of incoming data and location for output.

Submit an export job:

NotificationHubJob job = new NotificationHubJob();
job.setOutputContainerUri("container uri with SAS signature");
job = hub.submitNotificationHubJob(job);

Submit an import job:

NotificationHubJob job = new NotificationHubJob();
job.setImportFileUri("input file uri with SAS signature");
job.setOutputContainerUri("container uri with SAS signature");
job = hub.submitNotificationHubJob(job);

Wait until a job is done:

    job = hub.getNotificationHubJob(job.getJobId());
    if(job.getJobStatus() == NotificationHubJobStatus.Completed)

Get all jobs:

List<NotificationHubJob> jobs = hub.getAllNotificationHubJobs();

URI with SAS signature:

This URL is the URL of a blob file or blob container plus a set of parameters like permissions and expiration time plus signature of all these things made using account's SAS key. Azure Storage Java SDK has rich capabilities including creation of these URIs. As simple alternative, take a look at the ImportExportE2E test class (from the GitHub location) which has basic and compact implementation of signing algorithm.

Send Notifications

The Notification object is simply a body with headers, some utility methods help in building the native and template notifications objects.

  • Windows Store and Windows Phone 8.1 (non-Silverlight)
String toast = "<toast><visual><binding template=\"ToastText01\"><text id=\"1\">Hello from Java!</text></binding></visual></toast>";
Notification n = Notification.createWindowsNotification(toast);
  • iOS
String alert = "{\"aps\":{\"alert\":\"Hello from Java!\"}}";
Notification n = Notification.createAppleNotification(alert);
  • Android
String message = "{\"data\":{\"msg\":\"Hello from Java!\"}}";
Notification n = Notification.createFcmNotification(message);
  • Windows Phone 8.0 and 8.1 Silverlight
String toast = "<?xml version=\"1.0\" encoding=\"utf-8\"?>" +
            "<wp:Notification xmlns:wp=\"WPNotification\">" +
                "<wp:Toast>" +
                    "<wp:Text1>Hello from Java!</wp:Text1>" +
                "</wp:Toast> " +
Notification n = Notification.createMpnsNotification(toast);
  • Kindle Fire
String message = "{\"data\":{\"msg\":\"Hello from Java!\"}}";
Notification n = Notification.createAdmNotification(message);
  • Send to Tags
Set<String> tags = new HashSet<String>();
hub.sendNotification(n, tags);
  • Send to tag expression
hub.sendNotification(n, "foo && ! bar");
  • Send template notification
Map<String, String> prop =  new HashMap<String, String>();
prop.put("prop1", "v1");
prop.put("prop2", "v2");
Notification n = Notification.createTemplateNotification(prop);

Running your Java code should now produce a notification appearing on your target device.

Next Steps

This topic showed you how to create a simple Java REST client for Notification Hubs. From here you can: