Access ManagerPubNub provides builtin enterprise-grade security with fine-grained access control to all of your PubNub applications with PubNub Access Manager, Message Layer encryption with AES256, and Transport Layer Security with TLS and SSL.
|Grant||This function establishes access permissions for PubNub Access Manager (PAM) by setting the read or write attributes.|
|Grant Delete||This function establishes access permissions for PubNub Access Manager (PAM) by setting the Delete attribute.|
|Grant Manage||This function establishes access permissions for PubNub Access Manager (PAM) by setting the Manage attribute.|
|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 GroupsChannel 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 Channels||Add channel to a channel group.|
|List Channels In Channel Group||List all channels of a channel group.|
|Remove Channels||Remove channel from channel group.|
|Remove Channels Groups||Remove channel groups.|
|Add Message Actions||SDK has support to Add Message Actions|
|Get Message Actions||SDK has support to Get Message Actions|
|Remove Message Actions||SDK has support to Remove Message Actions|
Mobile PushPubNub's Mobile Push Gateway feature enables developers to bridge native PubNub publishing with third-party push notification services including Google FCM (Firebase Cloud Messaging) and Apple iOS APNs (Apple Push Notification service).
|Add Device To Channels||Enables push notifications on provided set of channels.|
|APNs Support||SDK has support to send notifications using the legacy APNs binary protocol|
|APNs2 Support||SDK has support to send notifications using APNs over HTTP/2|
|FCM Support||SDK has support to send notifications using FCM|
|List Channels From Device||List all channels on which push notification has been enabled.|
|Remove Device||Disable push notifications from all channels which is registered.|
|Remove Device From Channels||Disable push notifications on provided set of channels.|
NotifyAlerts from the SDK
|Request message count exceeded||When the number of messages arrived on a subscribe response are equal to or greater the number set in the init config, a new status message on the status callback, with the category PNRequestMessageCountExceededCategory, will be invoked.|
|Create Push Payload||The SDK has support to create the push payload for use in the appropriate endpoint calls.|
|Process pn_other in message||When a message with JSON key named `pn_other` is published and encryption is enabled, only the value of `pn_other` will be encrypted and the rest of the message will be in plain text. This feature is useful when you want to send out encrypted push notifications. On the subscribe end, if `pn_other` is detected in the received message and encryption is enabled, only the value of `pn_other` wil be decrypted. Rest of the message will be not be decrypted. Same goes for History and Fetch.|
|QueryParam in all API calls||The keys and values of the variable are passed as the query string parameters of the URL called by the API.|
|Telemetry||Sends back latency info to the server.|
PresencePubNub's Channel Presence empowers your applications to Track online and offline status of users and devices in realtime.
|Get State||Get state is used to get the key/value pairs specific to a subscriber UUID.|
|Heartbeat||Timeout events are triggered when the server does not hear a heartbeat from the client within a default timeout time of 280 seconds.|
|Here Now||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.|
|Set State||Set state is used to set key/value pairs specific to a subscriber UUID.|
|Where Now||Obtain information about the current list of a channels to which a UUID is subscribed.|
PublishPublish a message on a channel.
|Fire||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 Storage and Playback feature.|
|Publish Asynchronously||Publish the message asynchronously.|
|Publish RAW JSON||Publish JSON as is.|
|Publish using GET||Publish using HTTP GET|
|Publish using POST||Publish using HTTP POST|
|Publish with Metadata||Publish extra meta with the request used for Message Filtering.|
|Replication Flag||Controls whether the message should be replicated across stores.|
|Store Flag||Ability to skip message from storage.|
|TTL per published message||Offer the ability to set a per message time to live in storage.|
SignalsA lightweight alternative for small frequent indications exchanged between participants. Examples are typing indicators in chat, or geo-location information.
|Send a Signal||Has support to send a Signal|
StoragePubNub's Storage and Playback feature enables developers to store messages as they are published, and retrieve them at a later time.
|Count||Specifies the number of historical messages to return.|
|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.|
|Delete messages from storage||Removes the messages from the history of a specific channel.|
|Fetch messages from storage||This function fetches historical messages from multiple channels.|
|Fetch messages from storage with message actions||This function fetches historical messages from multiple channels with message actions data|
|Fetch messages from storage with meta||This function fetches historical messages from multiple channels with metadata|
|History with meta||The SDK has support to retrieve History with metadata|
|Include Timetoken||Whether event dates time tokens should be included in response or not.|
|Reverse||Traverse the timeline in reverse starting with the oldest message first.|
|Start End||Time token delimiting the start/end of time slice (exclusive) to pull messages from.|
SubscribeThis 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.
|Filter Expression||Stream Filter allows a subscriber to apply a filter to only receive messages that satisfy the conditions of the filter. The message filter is set by the subscribing client(s) but it is applied on the server side thus preventing unwanted messages (those that do not meet the conditions of the filter) from reaching the subscriber.|
|Message Actions events listener||Has support to listen to Action Events from Message Actions API|
|Publisher UUID||Has the publisher UUID of the published message.|
|PubSub v2 compatibility||Uses PubSub v2 to make subscribe calls.|
|Subscribe to channel groups||Ability to subscribe to channel groups.|
|Subscribe to channels||Ability to subscribe to channels.|
|Subscribe to presence channel groups||Ability to subscribe to presence channel groups.|
|Subscribe to presence channels||Ability to subscribe to presence channels.|
|Subscribe with timetoken||Subscribe with timetoken.|
|Wildcard subscribe||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 (.).|
TimeReturn a 17 digit precision Unix epoch from the server.
|Time||This function will return a 17 digit precision Unix epoch from the server.|
UnsubscribeUnsubscribe from a channel/channel group
|Unsubscribe from all||Unsubscribe from all channel/channel groups|
|Unsubscribe suppress leave events||Leave request will not be sent from the SDK, if set in config.|