Personal Access Tokens now available

August 2016 — this post originally featured on our previous blog at developers.intercom.io

Today we’ve released Personal Access Tokens, which — along with OAuth — will soon replace API Keys, as recently announced.

You’ll need to use Personal Access Tokens if you want to use the API to access your own Intercom data — if you’re currently using API Keys for this purpose, you will need to replace them with Personal Access Tokens.

New API Keys will be unavailable from 9th September

You will not be able to create new API Keys after Friday 9th September — after this date you will need to set up Personal Access Tokens instead.

• Personal Access Tokens are simple and instant to set up — here’s a guide.
• If you intend to create a publicly-available integration and therefore need access to other companies’ Intercom data, you will need to use OAuthrather than Personal Access Tokens.

If you’re confused about whether you need a Personal Access Token or OAuth, take a look at this guide or just send us a message and we’ll be happy to help.

You can generate Personal Access Tokens from your app settings menu in Intercom

A reminder on key dates for API Key deprecation:

• 9th September: users will no longer be able to generate new API Keys, so you’ll need to start using Personal Access Tokens instead — or, for public integrations, have OAuth in place in order to allow new users to authorize your service
• Jan 27th 2017: API Keys will no longer be accepted as a method for authorizing, so you’ll need either a Personal Access Token or OAuth to replace them — for public integrations, any existing users you have will need to be migrated to OAuth by this date to continue using your integration

Interested in building on the Intercom platform? Check out our Developer Hub to get started.