Patreon API no longer supplies user tier info

Hi there

A couple of weeks back, Patreon’s API responses on user tier selection changed. We managed to find a work around but at the end of last week they changed again and we now have no way of finding out from the API which tier a user has subscribed at.

In order to read benefit entitlement from the Patreon API we are using the following endpoint:

Originally we received the benefit IDs in the JSON response like so:
{
“data”: { … },
“included”: [

{
“type”: “benefit”,
“id”: “123456”
}

]
}

At some point in the past few weeks this stopped working, and we reviewed the API response again to receive benefit IDs like so:
{
“data”: { … },
“included”: [

{
“type”: “tier”,
“relationships”: {
“benefits”: {
“data”: [
{
“id”: “123456”
}
]
}
}
}

]
}

This method has stopped working too and in the JSON response we’re getting now there are no benefit IDs present at all, despite having “include=memberships.currently_entitled_tiers.benefits” specified in the API request. As such we are unable to determine if a Patreon user should have access to protected content or not.

Has anyone encountered the issue and solved it?

This should be working now.

Can you give me a little more detail? The adjustments we made after the first change still aren’t working.

I’m not sure if it helps but our Patreon integration is hosted at www.digitalfoundry.net

Thanks in advance.

OK, we’ve looked into this and now see that the code has reverted to its original form. We’ve rolled back our code to match and we’re back in business.

Thanks for this.

2 Likes