PubNub provides builtin enterprise-grade security with fine-grained access control to all of your PubNub applications with Access Manager, Message Layer encryption with AES256, and Transport Layer Security with TLS and SSL.
|This function establishes access permissions for Access Manager by setting the read or write attributes.
|Root permissions for the Access Manager
|When you init with secret key, you get root permissions for the Access Manager. With this feature you don't have to grant access to your servers to access channel data. The servers get all access on all channels.
Channel Groups allows PubNub developers to bundle thousands of channels into a group that can be identified by name. These Channel Groups can then be subscribed to, receiving data from the many backend-channels the channel group contains.
|Add channel to a channel group.
|Remove channel from channel group.
|Remove Channels Groups
|Remove channel groups.
|List Channels In Channel Group
|List all channels of a channel group.
PubNub's Channel Presence empowers your applications to Track online and offline status of users and devices in realtime.
|Obtain information about the current state of a channel including a list of unique user IDs currently subscribed to the channel and the total occupancy count of the channel.
|Obtain information about the current list of a channels to which a UUID is subscribed.
|Set state is used to set key/value pairs specific to a subscriber UUID.
|Get state is used to get the key/value pairs specific to a subscriber UUID.
Publish a message on a channel.
|Ability to skip message from storage.
|Publish RAW JSON
|Publish JSON as is.
|Publish with Metadata
|Publish extra meta with the request used for Message Filtering.
|Publish using GET
|Publish using HTTP GET.
|Fire method used for publishing. When a message is sent using fire, it will not be replicated to other Points of Presence, it will remain at the originating Point of Presence, and is not eligible for archiving via the Message Persistence feature.
Mobile Push Notifications
Mobile Push Notifications feature enables developers to bridge native PubNub publishing with third-party push notification services including Google Android Firebase Cloud Messaging (FCM) formerly known as Google Cloud Messaging (GCM) and Apple iOS Apple Push Notification Service (APNs).
|Add Device To Channels
|Enables push notifications on provided set of channels.
|Disable push notifications from all channels which is registered.
|List Channels From Device
|List all channels on which push notification has been enabled.
|Remove Device From Channels
|Disable push notifications on provided set of channels.
|SDK has support to send notifications using APNS.
|SDK has support to send notifications using APNS2.
|SDK has support to send notifications using FCM.
PubNub's Message Persistence feature enables developers to store messages as they are published, and retrieve them at a later time.
|Traverse the timeline in reverse starting with the oldest message first.
|Whether event dates time tokens should be included in response or not.
|Time token delimiting the start/end of time slice (exclusive) to pull messages from.
|Count of Messages on Channels
|The API is a history based API that simply does a mostly normal history operation but instead of returning the messages in a channel it returns the count of messages. Without actually calling history on those channels this API gives you the ability to say if there are messages in the chat channel you can go look at further.
|Specifies the number of historical messages to return.
Return a 17 digit precision Unix epoch from the server.
|This function will return a 17 digit precision Unix epoch from the server.
This function causes the client to create an open TCP socket to the PubNub Real-Time Network and begin listening for messages on a specified channel.
|Subscribe to channels
|Ability to subscribe to channels.
|Subscribe to channel groups
|Ability to subscribe to channel groups.
|Subscribe to presence channels
|Ability to subscribe to presence channels.
|Subscribe to presence channel groups
|Ability to subscribe to presence channel groups.
|Subscribe with timetoken
|Subscribe with timetoken.
|Wildcard subscribes allow the client to subscribe to multiple channels using wildcard. E.g., if you subscribe to a.* you will get all messages for a.b, a.c, a.x. The wildcarded * portion refers to any portion of the channel string name after the dot (.).
|Has the publisher UUID of the published message.