Skip to content

Device Registration API

In order to receive push notifications from Backendless, a device must be registered using the API documented below. Device registration may optionally include a list of messaging channels and/or an expiration date/time when the registration should be canceled.

Important

Push notifications can be published using either API or Backendless Console. When a push notification is published, it goes through a messaging channel. Channels provide a way to establish a level of filtering - devices registered with a channel will receive notifications published to the channel. However, there are other way to narrow down push notification delivery. For example, a push notification may be sent to a specific device or a group of devices.

If no channels are specified in the device registration call, Backendless registers the device with the default channel. If the device registration call references a non-existing channel, Backendless creates the channel and registers the device with it. Registration expiration is a point in time (expressed as a timestamp) when the device registration must expire. Backendless removes the device registration at the specified time and the device no longer receives published push notifications.

In order to receive push notifications on a mobile device, application running on the device must register with Backendless using the API call below:

Method

// registers device with FCM. Optionally, Backendless messaging channels and expiration timestamp for the Backendless registration can be specified.
Future<DeviceRegistrationResult> Backendless.messaging.registerDevice([List<String> channels, DateTime expiration]);

where:

Argument                Description
channels a collection of messaging channels the device registration will be associated with. Messages published to the channels will be delivered to the associated devices. For the methods without the argument, Backendless registers the device with the default channel;
expiration  a timestamp when the device registration should expire.

Return value

The DeviceRegistrationResult class. The object of that type contains the following properties:

Argument                Description
deviceToken device token received by the device as a result of registering with FCM. The value is a String object.
channelRegistrations a Map between Backendless channel name (key name in the map) and the registration ID of the device for that channel (value assigned to the key). When a device is registered with multiple Backendless messaging channels, this map will contain a mapping for each channel.

Errors:

The following errors may occur during the message publishing API call. See the Error Handling section for details on how to retrieve the error code when the server returns an error:

Error Code
Description
5004
Invalid expiration date. The expiration date must be after the current time.
8000
Property value exceeds the length limit. Error message should contain additional details about the violating property.

Example

List<String> channels = ["default"];
Backendless.messaging.registerDevice(channels).then((response) {
  print("Device registered!");
});