Shutting down OAuth1



Hello everyone,

Last year, we announced the launch of our OAuth 2.0 authentication protocol, which was replacing our existing OAuth1 system.

Today, we’re announcing that we’ll be shutting down our OAuth1 system on Friday, August 11th, 2017. At that time, all new authorizations will require you to use the OAuth 2.0 system.

To ease the the transition from OAuth1 to OAuth2, we’ve put together a guide that covers the differences between the two systems and what you’ll need to update:

If you have questions or run into any problems updating your app, check out the OAuth category here on the forums.


does this mean hapikey will go away too? or will that still work?


This will have no effect on hapikeys, and we don’t have any plans to change or remove API keys at this point so they’ll continue to work for the foreseeable future.


Will saved OAuth1 refresh tokens still work? We have quite a few automation integrations using that.


Existing Oauth1 refresh tokens will still be able to generate OAuth1 access tokens past the 8/11 deadline, but only until the end of the year, so you will need to have existing users re-authenticate your app with OAuth 2.0 to continue working past that.