All I need is to keep track who joins, updates, and deletes their membership and which specific tier

I am in a similar boat with @Deivedux. I pretty much just need to keep track of who is currently a member and what tier they are in. What appears to be a common and basic use case. If their card declines, they change tiers, they cancel their membership, etc. — I would like to know.

To be put as simply as possible;

Is this user currently paying me or not, and should they continue receiving the rewards for their tier, whichever one that may be?

@codebard states in this current thread, members:pledge triggers should suffice for this use case, which makes logical sense. However, I, like @Deivedux, have also stumbled across the thread of the poor soul who manually tested all the events — which seem to contradict the advice given in this thread. I would hate to have paying customers subscribe, only to realize I have been listening to the wrong event for the wrong scenario, and now I have no record of their existence outside of Patreon.

I have no problem using many webhook endpoints to listen to exactly what I need. The issue that I have is that the official documentation for the webhooks is at best unorganized and at worst misleading. I have spent a good few hours researching these webhooks and am yet to find answers to most of my questions. For example, what counts as a “pledge update”? Do I need to mark a member as having received their reward? Can I do it programmatically?

The sample webhook data differs wildly from the output from the webhook test outputs, and yet the test outputs are all nearly identical to each other. All the example data that us developers can get our hands on also has most of the information null’d out with hard to find explanations of their values. For example, who knew the Member resource is the data.attributes object in the webhook JSON?

This entire experience has been very frustrating and has me second guessing my intention to do business with Patreon. These aren’t the kinds of things that can be tested or YOLO’d in production.

To sum it up, I am looking for a webhook event, or (preferably) multiple events, that can tell me:

  • User (new/old/ancient) has started their subscription
  • User has changed their subscription tier
  • User has stopped their subscription (voluntarily or not)

Or put even more simply:

Is this user (still) paying me?

Now imagine my surprise when I find out pausing a pledge is a thing, and it is seemingly undocumented and without a webhook event.