Legacy Key Help

[BGB_Admin]

Hopefully quick question about the Legacy Key Sunsetting. We got an email about us using legacy keys during the recent brownouts. I added an SAK and was wondering if there are any additional steps needed. We have 3 third party authorized applications so will they be affected or need to be updated? The integrations in our app were done long before I worked at my company and I have very minimal coding knowledge so any help would be appreciated.

[TomScott]

Good afternoon!

If those third-party applications are using Legacy Keys, yes, they will need to be updated and using a current method. If they are using OAuth2 (and show up as “Third-Party Authorizations” in the app) then you don’t need to take any action regarding them.

Thanks,

• Tom Scott
  Keap API Engineer

[BGB_Admin]

Ok perfect! Just to be super clear. They are under “Third-Party Authorized Applications” so they are good to go?

[Pav]

@BGB_Admin, safe to use. Here is a link to a picture for your reference.

Steps in Migrating from Legacy Key to Service Account Key

Hi @Wendi_Dube, From what you are saying, it looks like you have nothing to do. Third-Party Authorized Applications are using OAuth, which requires a Keap User authorizing the connection between the application and your account. You just need to double check if there are any integrations using the Legacy API Key. Just for clarification, I have attached a picture for your and other people reference. [Keap API Settings]