(Apologies for not providing direct links to the material and documentation in question, your Discourse prevents me from linking)
Good morning!
I’m a member of the Keap (formerly Infusionsoft) API team and were directed to an integration hosted on your site with our prior brandmarks.
Normally we would be delighted to find new integrations that others had built on our platform, but it appears that the application (configuration screen shown below) uses a form of authentication (Legacy Key/encrypted key) which we will no longer be supporting on November 1st. It should be simple to be migrated to our Service Account Key method instead, or have more complexity if you would like to go full OAuth2 (as we use limited-lifetime refresh tokens).
We have migration documentation available on our developer site, and you can find information on how end-users can create and manage their authorizations there as well.
In addition, the article links from the configuration page no longer function, although the ones from the main listing page point correctly to a help article
describing that form of authentication, so they may just need to be replaced.
Our team monitors our Discourse community (linked through from our developer site) if you need any additional clarification or assistance!
Thank you!
- Tom Scott
Keap API Engineer