Yea as Codebard said, unless someone in the community has tiers to Patreon engineering it’s unlikely I can get the help I need here. I would just use the dollar amount instead of the tiers, but the tier issue causes error messages to show on any page using the API rendering it unusable.
Hi there. I have to caution it seems unfair to Skeddles and other developers, and a bad customer expectation to set, to suggest several years of no GitHub responses is Patreon’s version of ‘definitely not abandoned’. Some portion of the API development may have been ongoing, but this part – the customer facing/customer service portion — did not make that priority list. A 730 day lapse in customer service is a genuine dropped ball.
Okay. That said: What do your commitments look like, may I ask? How often are you planning to scan and answer questions on your GitHub repo? Also, have you hired a writer to put your replies together properly? Not only does it cut down on questions and misunderstandings, it helps with inadvertent implications like the one discussed in the first paragraph of my reply. Writers can keep you connected to the outside world and your community. They’re a real bonus.
I hope this mail isn’t coming across as harsh. My point is that internally pursing API improvements is only half the job. The other half (the customer service half) was abandoned, but doesn’t have to be in the future!
It definitely seems abandoned to me now. Parts of the documentation/examples are incorrect, extremely vague, or simply nonexistant. One would think a company as large as Patreon would, at the very least, be able to clean up the documentation?
1 Like
Well it looks like they’re doing something, because they managed to break something a day ago: Issue/Bug in Patreon API: last_charge_date empty for ALL patrons since 2020-09-03
1 Like
I read on this blog post that the API is no longer supported: https://support.patreon.com/hc/en-us/articles/206525646-Patreon-API
We are just about to start integrating Patreon OAuth in order to give perks to our users. Does this mean that it will possibly not work in the future?
Would appreciate a direct answer yes/no so we know how to best spent our resources.
Much thanks!
No worries, you can use the api to integrate Patreon. Even only through WP plugin, 4000+ sites are using the api - some pretty large sites. So it works fine. Hiccups happen due to infrastructure situation sometimes but that’s normal. But remember to use v2 clients with v2 endpoints and v2 calls. Just ignore the v1 documentation parts.
1 Like
I just spent several days implementing a Patreon integration to allow my site’s users to receive tiered benefits. I started with v2, since much of the documentation (including webhooks, where the v1 pledge webhooks are marked as deprecated) seems geared toward v2.
Only after 2 days of frustration and testing did I realize that the v2 API at least does seem to be abandoned, midway through its development apparently.
I luckily found this post and have been able to implement much of what I needed with v1. However, after reading more from developers I’m very concerned that the API will be completely abandoned in the near future. It is unacceptable that Patreon has not given a more thorough response than what is here.
Please respond, Patreon 
1 Like
As you can notice from the helpdesk article you linked, direct developer support is not being offered anymore for the api. But you can open topics and get community support at the developers’ forum:
As for development, you should definitely continue developing your app over api v2 specs. Api v1 will function for some time to come, but v2 is where the intended future of the api is at.
I’m surprised you see any future in either the v1 or the v2 API. Unless there’s a big change of priorities at Patreon, it seems like both are being left to rot. Webhooks are now half broken since Patreon added multicurrency support, and more recently even the v2 /campaign/members endpoint broke and is not returning the email address of the members.
I have to agree with @Dreaming_Spanish - my experience trying to develop against the v2 spec was incredibly frustrating. Even the simplest task like receiving the details of a member’s pledge levels in v2 seemed impossible and unnecessarily complicated. Again, I would ask for more clarity from the Patreon team.
Given the state of the API v2 documentation and the fact that most developers seem to be relying on v1, statements like,
Api v1 will function for some time to come
are pretty ominous.
It’s been well over a year since this thread started and the api has still yet to be made better.
I’m working to integrate a simple login application that can check the status of user logging in, verify their tier, and make changes when the user updates their patron status. With any other api/webhooks on another site, this would be easy and straight forward, but I have had a considerable amount of frustration working with patreon’s.
Very disappointed.
The API has been down again since the 22nd. No new, changed, or deleted pledges have been processed.
You can imitate the WordPress plugin’s call and usage patterns. They work pretty well and they are tested across large sites for a long duration now:
There is an efficient call there which not only gets a user’s profile info for registration/login but also the membership info to your campaign.
OAuth calls are in another class.
Are you having issues with calls to the api, or are the webhooks at integromat not working?
Call to API stopped working 3 days ago. Currently down. Webhooks at Integromat working fine right now.
So you are calling the api from your app and you cant have a response since 3 days ago?
As of the time I posted my last reply, but it started working again not too long after.
That sounds pretty odd. Such a situation with api calls not working was not reported by anybody in that period. This may be a case of your server or service provider blocking IPs to Patreon (or cloudflare) or vice versa.
New developer here…what is the consensus on developing a new app that relies on Patreon’s oAuth API? I built an app that planned to curate content based on subscription tier by having users log in using Patreon so I can validate their tier.
However, my impression of the API is that (1) No or little support and (2) Has stability issues, and (3) Probably abandoned at some point in the near future. (Makes me start to reconsider my original authorization plan, carrier pigeons.)
Should I reconsider the API and look for other options?
Thank you for the advice.
Jeff
Chief Lab Minion
-
Api has enough support to enable app building.
-
There are some stability issues that are being worked on.
-
Nope.
-
No need.
…
Just make sure that you use v2 calls with v2 endpoints though. v1 is going to be deprecated.