Upgrading to the new API

Thanks to feedback from the plugin developers, we have updated the way the authentication API works slightly. Basically, we how create a hex digest for the signature instead of a binary digest, base64 encoded, and url escaped. But you shouldn’t need to know that. Full details in the docs.

We are rolling out this new version to production alongside the old REST API, which should now be considered deprecated.

Upgrading your apps to use the new authenticated REST API

Our Ruby Gem has now been updated (version 0.4.0 and above only supports the authenticated api), and the other libraries are either done or nearly done.

Upgrade path for Ruby

Get the latest version of the gem in your app:

gem install pusher

Go to your dashboard from the Pusher site and copy your security credentials (you now need application id, key, and secret). Once you’ve added these to your app things should Just Work.

Upgrade path for other languages

We are working with the maintainers of the PHP, Perl, Python, Node.js and Objective-C libraries to get them updated. The Objective-C and PHP library are finished, and the others are on the way. We will post about them here, and also tweet when they are ready.

If you are using another language and need help integrating, please get in touch with us via support@pusher.com. And if you haven’t done so already, feel free to create a free Pusher account and let us know what you think!

Ready to begin?

Start building your realtime experience today.

From in-app chat to realtime graphs and location tracking, you can rely on Pusher to scale to million of users and trillions of messages