“Legacy Key Auth has been turned off” doesn’t mean what I thought it meant. My understanding is that the Legacy API key needed to be presented with each request and so turning it off means every request will now be rejected (stopping the Unbounce native Keap integration dead in its tracks). But perhaps instead authentication persists for some indefinite period of time and it’s the ability to refresh this auth that has been turned off??
The second option doesn’t seem right to me, so is it reasonable to conclude that Unbounce has bought an extension?
I replied to someone asking about Unbounce in the Forum Post below. Unfortunately, they did not reply back about the Service Account Key.
In their documentation it says the following below.
When in your Infusionsoft account, be sure to select the option to Generate Legacy Key. Though a Service account key works the same as a Legacy Key, you can only use one at a time.
What you can do is to generate a Service Account Key, and replace the Legacy API Key in the Account.
If it works all okay, then you know Unbounce has made the changes.