Changes due to the sunsetting of Keap legacy API keys:
- Implemented support for Service Account Keys.
- Modified the SDK to accommodate both legacy API keys and Service Account Keys.
- ntroduced new security key options that replace the first six characters of the legacy API key. By pre-filling the initial six characters of the legacy API key, we ensure that operations such as HTTP_POST, autologin, and others will continue to work without interruption. This approach guarantees seamless functionality within Keap action sets, campaigns, thank you pages, and more.
According to Keap: “If you use an alternate language to integrate or you are not on the latest version of our PHP SDK, you can continue to use your Legacy Key to make calls against the Keap API for now, but you will need to make some minor adjustments to your API calls.” Our understanding of this is that legacy keys will work even after the sunset date in our case. We have made the necessary adjustments to the SDK as referenced by Keap.
However, we recommend the use of an Service Account Key.
Find more information about sunsetting the legacy API keys here: https://help.keap.com/help/sunsetting-legacy-api-keys