Keap legacy API key migration: what iMEMBER360 customers need to know

Where things stand today

Keap's legacy API key migration deadline and brownout period, including the October 31, 2024 milestone, are now in the past. Any iMEMBER360 site that is still configured with a legacy API key should be reviewed and moved to a supported authentication method.

Please keep iMEMBER360 on a current supported version and replace any legacy API key with a Keap Service Account Key unless your site is already using OAuth2 as configured.

If you are using OAuth2 authentication in iMEMBER360, the legacy API key brownouts were not the primary connection path for that setup. However, older configurations may still contain a legacy key as a fallback or historical setting, so it is worth replacing it with a Service Account Key during maintenance.

If you do not see an update notification for iMEMBER360, go to the plugins listing in your WordPress dashboard and check whether your license and update channel are active. If you are unsure which authentication method your site uses, contact support before making changes on a live membership site.

If you're facing any issues or need assistance, don't hesitate to submit a support ticket to imsupport@helpcenter360.com.

For more information, please refer to our v5.4.0 changelog and Keap's website about generating a Service Account Key at https://developer.infusionsoft.com/pat-and-sak/.