Webhook member IDs changed from integers to UUID?

API Feedback
1

So I’ve encountered some problems with webhook responses recently - I noticed that with the V2 API endpoints, member IDs in the JSON response are suddenly UUID strings instead of integers-as-string IDs like before (at least in case of what was a user ID, to which a pledge belongs to).

Can you shed some light on the reasoning behind this? Which distinction should we assume going forward, forget about user IDs and store membership UUIDs instead to check access rights?

2

So, if you look at https://docs.patreon.com/#user-v2, you’ll see that users have memberships, and they are distinct objects. Memberships represent a user’s relationship to a campaign, a user is a user.

2 Likes