Get started

Preparing iMEMBER360 for Keap REST API v2

Migration Keap REST API v2

Overview

Keap has announced that the legacy XML-RPC API will be shut down on December 31, 2026. This affects many long-standing Keap integrations, including iMEMBER360.

iMEMBER360 version 6.0.0 is planned as the release that completes the transition from Keap XML-RPC to Keap REST API v2 wherever Keap provides a supported replacement.

Until then, iMEMBER360 will continue to receive non-breaking updates designed to make the transition smoother. Existing legacy features will continue to work until the XML-RPC shutdown date, but some older Keap features cannot be migrated one-to-one because they are no longer supported in the same way by Keap REST API v2.

Why this migration matters

For many years, iMEMBER360 supported very granular Keap-powered membership workflows. That depth was possible because Keap’s XML-RPC API exposed functionality that was not available through earlier REST APIs.

Keap REST API v2 is the future path, but it does not provide full feature parity with XML-RPC, and full parity should not be expected. As a result, some legacy Keap features will need to be replaced, simplified, or phased out as part of the migration.

This is not an immediate break. The goal of the transition period is to give site owners enough time to prepare their Keap setup before December 31, 2026.

What will continue to work during the transition

Until the shutdown date, current iMEMBER360 legacy features will continue to work as they do today.

Between now and iMEMBER360 6.0.0, we plan to release several non-breaking updates. These updates are intended to prepare sites for the REST API transition without forcing immediate workflow changes.

Where Keap REST API v2 provides a supported replacement, iMEMBER360 will migrate those features. Where Keap no longer provides an equivalent API feature, we will document the change and provide recommended migration paths where possible.

What site owners should prepare now

The most important preparation work happens inside Keap.

1. Replace Action Sets with modern Keap automations

Legacy Action Sets are one of the most important areas to review.

If your site uses iMEMBER360 features, shortcodes, widgets, or integrations that run Keap Action Sets, those workflows should be moved to modern Keap automations wherever possible.

For most sites, the simplest migration path is to trigger automations by applying a Keap tag.

Recommended approach:

  1. Create a new Keap tag that represents the trigger.
  2. Build a Keap automation that starts when that tag is applied.
  3. Replace the Action Set-based workflow with the new tag-triggered automation.
  4. Update the related iMEMBER360 shortcode or setting to apply the tag instead of running the Action Set.

This is the cleanest migration path for most customer-managed workflows because tag assignment is supported by Keap REST API v2 and is easy to understand, test, and audit.

2. Keep API Goals where they are intentionally used

Keap API Goals, also called Automation Goals, are different from legacy Action Sets.

API Goals are expected to remain supported because Keap REST API v2 provides a newer endpoint for triggering automation goals. This means existing iMEMBER360 workflows that intentionally use API Goals may not need to be replaced with tag-triggered automations.

However, API Goals should still be reviewed and tested during the migration period.

In short:

  • Action Sets should be replaced.
  • Legacy Follow-Up Sequences should be replaced.
  • API Goals may continue to be used where they are intentionally configured and tested.
  • Tag-triggered automations remain the recommended migration path for simpler customer-managed workflows.

3. Replace legacy Follow-Up Sequences

Legacy Follow-Up Sequences should also be reviewed and migrated.

If your site still depends on old Follow-Up Sequence logic, those flows should be rebuilt using Keap’s current Automation Builder. Where possible, trigger the new automation with tags rather than relying on legacy sequence assignment.

4. Move away from Keap’s standard Password field

Keap’s standard Password field is not expected to be supported in the same way through REST API v2.

If your iMEMBER360 setup still uses the standard Keap Password field, you should migrate to a dedicated custom field for storing the member password.

If your site already uses a custom password field, you can skip this step.

Recommended approach:

  1. Create or identify a custom text field in Keap for the member password.
  2. Configure iMEMBER360 to use that custom password field.
  3. Test login, password generation, password reset, and new member registration flows.
  4. Confirm that existing members can still log in correctly.

5. Review FileBox-based workflows

Keap FileBox functionality is a legacy area that may not have a clean REST API v2 replacement.

If your site allows members to upload files to Keap, download files from Keap, or display Keap FileBox files through iMEMBER360 shortcodes, those workflows should be reviewed.

In many cases, a better long-term replacement may be a WordPress media workflow, Amazon S3, a secure file plugin, or another dedicated document storage solution.

6. Review older ecommerce and billing workflows

Some billing and payment functionality can be migrated because Keap now provides newer payment method APIs.

For example, iMEMBER360’s newer credit-card add flow is already aligned with Keap’s newer payment method approach.

However, older ecommerce workflows, invoice handling, subscription handling, one-click order processing, and legacy credit-card field displays still need careful review because not every old Keap billing object or field has a direct REST API v2 equivalent.

If your site uses iMEMBER360 billing, invoice, subscription, or credit-card shortcodes, review the separate compatibility list linked below.

Affected legacy features, shortcodes, and settings

We maintain a separate technical compatibility list for affected legacy functionality.

That list includes shortcodes, admin settings, widgets, integrations, and features that are:

  • expected to migrate cleanly
  • expected to require Keap-side changes
  • under review
  • likely to be deprecated because Keap REST API v2 does not provide a replacement

View the compatibility list here:

Affected iMEMBER360 legacy features, shortcodes and settings

Keeping this information separate allows us to update the technical list as Keap’s REST API v2 evolves and as iMEMBER360 migration work progresses.

Important note about custom code

If your site includes custom code, please review it carefully before updating during the migration period.

Custom code may break if it:

  • calls Keap XML-RPC methods directly
  • uses iMEMBER360 internal API wrappers in unsupported ways
  • reads or writes directly to iMEMBER360 database tables
  • depends on legacy Keap objects that no longer exist in REST API v2
  • assumes old Action Set, Follow-Up Sequence, FileBox, billing, or credit-card table behavior

Direct database access and unsupported custom integrations cannot be guaranteed during the migration to iMEMBER360 6.0.0.

If your site uses custom code, involve your developer before each iMEMBER360 update.

What you should do now

To prepare for a smooth transition:

  1. Identify any Action Sets used by your membership site.
  2. Rebuild those workflows as tag-triggered Keap automations where practical.
  3. Review existing API Goals and confirm they are still intentional and tested.
  4. Replace legacy Follow-Up Sequences with current Keap Automation Builder flows.
  5. Confirm that iMEMBER360 uses a custom password field, not Keap’s standard Password field.
  6. Review any FileBox-based upload or download workflows.
  7. Review billing, invoice, subscription, and credit-card shortcodes if your site uses them.
  8. Ask your developer to audit any custom code before updating.

Timeline

Until December 31, 2026, legacy XML-RPC-based features are expected to continue working.

Before that date, iMEMBER360 will receive non-breaking updates to support the transition.

iMEMBER360 6.0.0 is planned as the full REST API v2 migration release. Features that can be migrated safely will be moved to REST API v2. Features that depend on XML-RPC-only Keap functionality will be documented, replaced where possible, or deprecated with guidance.

Summary

The Keap XML-RPC shutdown is an important platform change, but it does not require immediate panic.

Most site owners can prepare by moving legacy Action Set logic to modern Keap automations, replacing old Follow-Up Sequences, using a custom password field, and reviewing older FileBox or billing workflows.

The earlier these steps are completed, the smoother the transition to iMEMBER360 6.0.0 will be.