Keap has deprecated Legacy API Keys, this means Legacy API keys will no longer work.
To fix this, just update iTracker360 to use OAuth (which is recommended) or a Service Account Key. Don’t bother with the Personal Access Token since this does not give admin access. iTracker360 needs to be able to update any lead that comes through, not just the leads that are assigned to a single user who generated the personal access token.
To update your API Key – just go to “Setup & Testing” -> “Setup API Key” when you are logged into the members site.
Question: Can you use both OAuth and a SAK (service account key) ?
Yes – we recommend using OAuth since this has higher API throttling limits. If you connect both, then we’ll use OAuth first, but if that fails for some reason, then we will use the SAK as a backup connection.
Question: If I haven’t updated my legacy key yet, what happens?
At some point we will not be able to connect to the Keap API. So you are encouraged to update your API connection inside iTracker360 to avoid service disruption.