In order to use this library, you need to have an account on http://pusher.com. After registering, you will need the application credentials for your app.
You need to be running Node.js 0.8+ to use this library.
$ npm install pusher
In order to use the library in a Parse Cloud module, install the module into your cloud/modules path:
$ npm install pusher --prefix cloud/modules
Then to build the file bundle for Parse Cloud:
$ cd cloud/modules/pusher
$ npm run parse-build
To import Pusher:
var Pusher = require('cloud/modules/node_modules/pusher/parse');There are 3 ways to configure the client. First one is just using the Pusher constructor:
var Pusher = require('pusher');
var pusher = new Pusher({
appId: 'APP_ID',
key: 'APP_KEY',
secret: 'SECRET_KEY',
encrypted: ENCRYPTED, // optional, defaults to false
host: 'HOST', // optional, defaults to api.pusherapp.com
port: PORT, // optional, defaults to 80 for unencrypted and 443 for encrypted
cluster: 'CLUSTER', // optional, if `host` is present, it will override the `cluster` option.
});For specific clusters, you can use the forCluster function. This is the same as using the cluster option in the constructor.
var Pusher = require('pusher');
var pusher = Pusher.forCluster("CLUSTER", {
appId: 'APP_ID',
key: 'APP_KEY',
secret: 'SECRET_KEY',
encrypted: ENCRYPTED, // optional, defaults to false
port: PORT, // optional, defaults to 80 for unencrypted and 443 for encrypted
});You can also specify auth and endpoint options by passing an URL:
var Pusher = require('pusher');
var pusher = Pusher.forURL("SCHEME://APP_KEY:SECRET_KEY@HOST:PORT/apps/APP_ID");You can pass the optional second argument with options, as in forCluster function.
This is useful for example on Heroku, which sets the PUSHER_URL environment variable to such URL, if you have the Pusher addon installed.
There are a few additional options that can be used in all above methods:
var Pusher = require('pusher');
var pusher = new Pusher({
// you can set other options in any of the 3 ways described above
proxy: 'HTTP_PROXY_URL', // optional, URL to proxy the requests through
timeout: TIMEOUT, // optional, timeout for all requests in milliseconds
keepAlive: KEEP_ALIVE // optional, enables keep-alive, defaults to false
});Asynchronous methods on the Pusher class (trigger, get and post) take an optional callback as the last argument. After performing the request, the callback is called with three arguments:
- error - if the request can't be performed or returns an error code, error will contain details, otherwise it will be null
- request - the request object
- response - the response object - can be undefined if response was not received
All operational errors are wrapped into a Pusher.RequestError object.
In case accessing data for invalid WebHooks, an Pusher.WebHookError exception will be thrown from the called method. It is recommended to validate the WebHook before interpreting it.
To send an event to one or more channels use the trigger function. Channel names can contain only characters which are alphanumeric, '_' or '-' and have to be at most 200 characters long. Event name can be at most 200 characters long too.
pusher.trigger('channel-1', 'test_event', { message: "hello world" });To trigger an event on multiple channels:
pusher.trigger([ 'channel-1', 'channel-2' ], 'test_event', { message: "hello world" });If you wish to send multiple events in a single HTTP request, you can pass an array of events to pusher.triggerBatch. You can send up to a maximum of 10 events at once.
var events = [{
channel: "channel-1",
name: "test-event-1",
data: {message: "hello world"}
},
{
channel: "channel-2",
name: "test-event-2",
data: {message: "hello another world"}
}];
pusher.triggerBatch(events);You can trigger an event to at most 10 channels at once. Passing more than 10 channels will cause an exception to be thrown.
In order to avoid the client that triggered the event from also receiving it, the trigger function takes an optional socketId parameter. For more informaiton see: http://pusher.com/docs/publisher_api_guide/publisher_excluding_recipients.
var socketId = '1302.1081607';
pusher.trigger(channel, event, data, socketId);Pusher now allows sending native notifications to iOS and Android devices. Check out the documentation for information on how to set up push notifications on Android and iOS. There is no additional setup required to use it with this library. It works out of the box wit the same Pusher instance. All you need are the same pusher credentials.
The native notifications Server API is hosted at nativepush-cluster1.pusher.com and only accepts https requests.
You can send pushes by using the notify method, either globally or on the instance. The method takes three parameters:
interests: An Array of strings which represents the interests your devices are subscribed to. These are akin to channels in the DDN with less of an epehemeral nature. Note that currently, you can only send to, at most, ten interests.data: The content of the notification represented by a Hash. You must supply either thegcmorapnskey. For a detailed list of the acceptable keys, take a look at the docs.callback: A callback function which is passed three arguments: a (possibly null) error, a request object, and a response object.
Example:
var data = {
apns: {
priority: 5,
aps: {
alert: {
body: 'tada'
}
}
}
}
pusher.notify(["my-favourite-interest"], data, function(error, req, res) {
console.log(error, req, res);
})Push notification requests, once submitted to the service are executed asynchronously. To make reporting errors easier, you can supply a webhook_url field in the body of the request. This will be used by the service to send a webhook to the supplied URL if there are errors.
You may also supply a webhook_level field in the body, which can either be INFO or DEBUG. It defaults to INFO - where INFO only reports customer facing errors, while DEBUG reports all errors.
For example:
var data = {
"apns": {
"aps": {
"alert": {
"body": "hello"
}
}
},
'gcm': {
'notification': {
"title": "hello",
"icon": "icon"
}
},
"webhook_url": "http://yolo.com",
"webhook_level": "INFO"
}NOTE: This is currently a BETA feature and there might be minor bugs and issues. Changes to the API will be kept to a minimum, but changes are expected. If you come across any bugs or issues, please do get in touch via support or create an issue here.
To authorise your users to access private channels on Pusher, you can use the authenticate function:
var auth = pusher.authenticate(socketId, channel);For more information see: http://pusher.com/docs/authenticating_users
Using presence channels is similar to private channels, but you can specify extra data to identify that particular user:
var channelData = {
user_id: 'unique_user_id',
user_info: {
name: 'Phil Leggetter'
twitter_id: '@leggetter'
}
};
var auth = pusher.authenticate(socketId, channel, channelData);The auth is then returned to the caller as JSON.
For more information see: http://pusher.com/docs/authenticating_users
It's possible to query the state of the application using the pusher.get function.
pusher.get({ path: path, params: params }, callback);The path property identifies the resource that the request should be made to and the params property should be a map of additional query string key and value pairs.
Params can't include following keys:
- auth_key
- auth_timestamp
- auth_version
- auth_signature
- body_md5
The following example provides the signature of the callback and an example of parsing the result:
pusher.get({ path: '/channels', params: {} }, function(error, request, response) {
if (response.statusCode === 200) {
var result = JSON.parse(response.body);
var channelsInfo = result.channels;
}
});pusher.get({ path: '/channels', params: params }, callback);Information on the optional params and the structure of the returned JSON is defined in the REST API reference.
pusher.get({ path: '/channels/[channel_name]', params: params }, callback);Information on the optional params option property and the structure of the returned JSON is defined in the REST API reference.
pusher.get({ path: '/channels/[channel_name]/users' }, callback);The channel_name in the path must be a presence channel. The structure of the returned JSON is defined in the REST API reference.
The library provides a simple helper for WebHooks, which can be accessed via Pusher instances:
var webhook = pusher.webhook(request);Requests must expose following fields:
- headers - object with request headers indexed by lowercase header names
- rawBody - string with the WebHook request body
Since neither Node.js nor express provide the body in the request, your application needs to read it and assign to the request object. See examples/webhook_endpoint.js for a simple webhook endpoint implementation using the express framework.
Headers object must contain following headers:
- x-pusher-key - application key, sent by Pusher
- x-pusher-signature - WebHook signature, generated by Pusher
- content-type - must be set to application/json, what Pusher does
After instantiating the WebHook object, you can use its following methods:
Validates the content type, body format and signature of the WebHook and returns a boolean. Your application should validate incoming webhooks, otherwise they could be faked.
Accepts an optional parameter containing additional application tokens (useful e.g. during migrations):
var webhook = pusher.webhook(request);
// will check only the key and secret assigned to the pusher object:
webhook.isValid();
// will also check two additional tokens:
webhook.isValid([{ key: "x1", secret: "y1" }, { key: "x2", secret: "y2" }]);Returns the parsed WebHook body. Throws a Pusher.WebHookError if the WebHook is invalid, so please check the isValid result before accessing the data.
// will return an object with the WebHook data
webhook.getData();Please read the WebHooks documentation to find out what fields are included in the body.
Returns events included in the WebHook as an array. Throws a Pusher.WebHookError if the WebHook is invalid, so please check the isValid result before accessing the events.
// will return an array with the events
webhook.getEvents();Returns the Date object for the time when the WebHook was sent from Pusher. Throws a Pusher.WebHookError if the WebHook is invalid, so please check the isValid result before accessing the time.
// will return a Date object
webhook.getTime();If you wanted to send the REST API requests manually (e.g. using a different HTTP client), you can use the createSignedQueryString method to generate the whole request query string that includes the auth keys and your parameters.
pusher.createSignedQueryString(options);The only argument needs must be an object with following keys:
- method - the HTTP request method
- body - optional, the HTTP request body
- params - optional, the object representing the query params
Query parameters can't contain following keys, as they are used to sign the request:
- auth_key
- auth_timestamp
- auth_version
- auth_signature
- body_md5
The tests run using Mocha. Make sure you've got all required modules installed:
npm install
You can run local integration tests without setting up a Pusher app:
node_modules/.bin/mocha tests/integration/**/*.js
In order to run the full test suite, first you need a Pusher app. When starting mocha, you need to set the PUSHER_URL environment variable to contain your app credentials, like following:
`PUSHER_URL='http://KEY:[email protected]/apps/APP_ID' node_modules/.bin/mocha $(find tests)`
This library is based on the work of:
- Christian Bäuerlein and his library pusher.
- Jaewoong Kim and the node-pusher library.
This code is free to use under the terms of the MIT license.