Hi there! We’ve been listening to the feedback that you and other Patreon API developers have been giving us over the past months about how our API, and our platform as a whole, could be better for developers, creators, and patrons. We’ve taken this feedback, added enhancements to respect the privacy of our creators and patrons, and turned that into a new version of our API, which is available in open beta today.
If you have created a client solely for use with the Patreon Wordpress plugin, you can ignore most of this message. Instructions on how to use the Wordpress plugin with APIv2 will be available soon.
So what’s new?
- Members : We’ve taken the feedback you have about working with pledges and turned that into a more robust data model giving you more detail about a creator’s patrons, including member lifetime, charge status, and last charge date.
- Webhooks : APIv2 lets developers create webhooks programmatically on the creator’s behalf, so your app can subscribe to real-time updates about what’s changing with a creator’s patrons.
- Scopes : These new features are coming with a new set of scopes, to better protect the privacy of creators and patrons and to let developers get exactly what they need from our API.
- Less friction : If you’re building an app that you want many creators to use, you can now do this in a self-service manner without a manual approval process with our team. Go build great things for creators!
Where do we go from here? Well, we’ve got new sections on our developer documentation page explaining the changes and the new APIs. APIv2 is in public beta TODAY, but APIv1 isn’t going away yet. In fact, you can use the new endpoints interchangeably during the transitionary phase (although the APIv1 endpoints will be going away in the future). We’ll give lots of notice here when APIv2 moves out of beta, and at that point we’ll talk about the future of APIv1.
Thanks for reading, and thanks for developing with Patreon!
The Patreon Platform Team