Keap Resthooks

Keep WordPress access aligned with Keap

Keap resthooks help iMEMBER360 keep local membership data in step with your CRM. When supported Keap contact or tag records change, iMEMBER360 can receive the update, refresh the relevant local cache, and make the next WordPress access check reflect the current Keap record.

Built for CRM-driven membership sites

This matters most when Keap is the source of truth for access. A campaign may add or remove a membership tag, an admin may edit a contact, or a tag may change inside Keap. Resthook support reduces the gap between those CRM-side changes and the protected WordPress experience your members see.

What resthooks support

  • Contact updates — detect supported contact edits and mark local membership data for refresh
  • Contact deletion — respond when a Keap contact tied to a WordPress member is removed
  • Tag changes — refresh the local tag cache when Keap contact-group data changes
  • Activity logging — record resthook processing in the same API log used for troubleshooting

Where teams use them

  • Keeping protected pages aligned with tag changes made inside Keap
  • Reducing stale access decisions when a contact moves between membership tiers
  • Refreshing local tag data after Keap tag edits
  • Troubleshooting CRM-to-WordPress access changes from the Activity Log

How it pairs with the rest of iMEMBER360