If your creator API key has the member_events scope, you can call get_member_events (as an MCP tool or via GET /creator-api/v1/member-events/) to see counts of who joined, who left, and why.

It covers memberships, standalone communities, and courses or digital products.

For memberships, get_member_events breaks down leaves by how the membership ended and what the member said on the cancel survey.

This breakdown always adds up to the same cancelled-member count your subscriptions tool reports, so the two stay consistent.

Since 9 March 2026, the cancel survey has been sending a blank reason. Because of this, most recent paid membership cancellations show as 'no reason given' rather than a specific reason.

For a standalone community, get_member_events reports joins, leaves, leave reasons, and current members.

Community access that comes bundled with a membership, course or other product is not included here. That matches how your subscriptions tool and the Insights chart already treat bundled community access.

One limitation to know: get_member_events cannot tell the difference between a paid community cancellation and a failed payment. Both are recorded the same way.

For courses and digital products, get_member_events reports how many times access was given and how many access periods ran out.

When access is removed another way, such as a refund, a failed payment, or a manual removal, the underlying record is deleted. In that case, 'access removed' comes back as null with a reason, rather than a count.

get_member_events only ever gives you aggregate counts. It never returns names, emails, IDs, or any per-person rows.

It also never echoes back what a customer actually typed as their cancellation reason, and it does not calculate a churn rate or ratio for you.

If you get stuck, message us from the chat bubble and we will help.