Pub/Sub notifications provide a way for you to receive alerts about newly enrolled devices, device reports, and recently issued commands.
To set up Pub/Sub notifications, you need to enable the Pub/Sub API and create a topic. To receive messages published to a topic, create a subscription to that topic. The subscription connects the topic to a subscriber application that receives and processes messages published to the topic. After you create a subscription, you need to grant Android Device Policy permission to publish to your topic.
1. Enable the Pub/Sub API for your project
2. Create a topic
After enabling the API, you need to create a topic that Android Device Policy can publish notifications to. There are two ways to create a topic:
After creating a topic, take note of the topic name.
3. Create a subscription
A subscription captures the stream of messages published to a given topic. There are two ways to create a subscription:
4. Grant Android Device Policy the right to publish to your topic
You need to give firstname.lastname@example.org permission to publish to your topic. There are two ways to grant publishing rights:
a. Manually in the Google Cloud Platform Console.
- Add email@example.com as a member to your topic.
- Click Select a role > Pub/Sub > Pub/Sub Publisher.
b. Using the Pub/Sub API (see Access Control via the Google Cloud Pub/Sub IAM API)
5. Update enterprise to support notifications
To connect notifications about an enterprise to the topic you created, call
and specify the following parameters:
pubsubTopic: The name of your pub/sub topic in the form
enabledNotificationTypes: Include all the notification types you wish to receive. Choose from
6. Use the Pub/Sub API to get notifications
A subscription can use either the push or pull mechanism for message delivery. Guidelines and directions on how to receive notifications through both of these mechanisms are available in the Pub/Sub Subscriber Guide.
Messages take the form of a
attributes field of the message contains an attribute with key
notificationType and value set to the notification type that triggered the
data field of the message contains the JSON
representation of the resource that was updated, encoded as a UTF-8 string. The
notifications and their corresponding resource types are as follows:
COMMANDnotifications use the resource type Operation.
USAGE_LOGSnotifications use the resource type UsageLogEvent.
STATUS_REPORTnotifications use the resource type Device.
When setting the
pubsubTopic on an Enterprise, an initial message will be
notificationType set to
test. This message is sent to verify
Android Device Policy has the publish permission on the topic and should be