Update: New API Key deprecation deadline

New API Keys will be unavailable from March 2017

Earlier this year we announced the upcoming deprecation of API Keys (you can read about why in the original post, but in short we want to make using integrations much more seamless and secure for our users).

Our initial deadline for full deprecation was January 2017, but we’re extending this a little to give you more time to prepare.

As a reminder, the deprecation of API Keys means that:

• if you’re using the API for personal use to access your own Intercom data, you will now need to use a Personal Access Token
• if you’ve built an integration that accesses other users’ data, you must implement OAuth and replace any existing API Key authorizations with OAuth

We’ll be removing the ability for users to create new API Keys in late March 2017, at which point any integrations not yet using OAuth will be unable to accept new users (as users won’t be able to generate an API Key for authorization). All Intercom-built integrations will be updated to OAuth by this time.

We’re also here to help— if you need help implementing OAuth or moving to Personal Access Tokens please send us a message via our website and we’ll be happy to help.

Existing API Keys will continue to work until they are fully deprecated, which will be mid-2017. However, we recommend you upgrade ASAP — particularly those with public integrations, as OAuth is a requirement to join our new Developer Program and get listed on our integrations page.

As before, we’ll continue to post reminders here on the developer blog and on Twitter.