Sunsetting Legacy API Keys What do I need to do?

[gasand]

Hi everyone, thanks for your work!

In a recent post, which can be found at this link: https://help.keap.com/help/sunsetting-legacy-api-keys, Keap announced the sunsetting of Legacy API Keys.

I’ve inherited a piece of code that uses your library to connect to Infusionsoft, and it works pretty well. However, I’ve realized that I'm using a Legacy API Key through your library.

Now, I’m not sure what steps I need to take. Is it just a matter of generating a new key and continuing to use your library, or is there more that I need to do?

[Fraanv1]

Hi, same issue here

[gasand]

Hi @Fraanv1 I've fixed the problem this way:

• downloaded this repository
• locate the CreateProxyManager method in InfusionsoftProxy.cs
• Add this row befor the return: proxy.Headers.Add("X-Keap-API-Key", _configuration.GetApiKey());

Rebuilt the .dll Now I use my version of the dll an I can use a SAKapiKey

Hope this helps you!