The Zoom API limitation currently doesn’t fetch registrants with “cancelled by self” which is a huge blocker for our team to move ahead with the nurture reach-out flows.
Hey,
Ran into something similar while working with registrant data flows. The limitation around “cancelled by self” not being included can definitely break downstream automation, especially for nurture or re-engagement logic.
One workaround that helped us partially was relying more on webhook events (like meeting registration updates) and maintaining a separate log of status changes on our end. It’s not ideal, but it gave us better visibility compared to relying only on the fetch endpoints.
Not sure if you’ve already explored that path, but curious — are you currently tracking registrant state changes via webhooks or only pulling via API?