Patreon API
/api/oauth2/api/* version retirement
Stopped workingSubscribe to Patreon APIShare
Patreon retired API v1 on October 7, 2026. Calls to endpoints under /api/oauth2/api/* now fail. All v1 endpoints stopped responding after that date.
Calls it hits
/api/oauth2/api/*
What to use instead of these calls
Move to API v2 under /api/oauth2/v2/, using endpoints such as GET /api/oauth2/v2/identity, /api/oauth2/v2/campaigns, and /api/oauth2/v2/campaigns/{campaign_id}/members while requesting fields and include explicitly. Switching requires a new v2 client from the Clients & API Keys page and its scopes rather than just changing an identifier. Creators who requested an extension retain access to v1 until January 20, 2027.
API v2 needs a new v2 client from the Clients & API Keys page and its scopes; creators who requested an extension keep v1 until January 20, 2027.
In Patreon API's words
All v1 endpoints (served under patreon.com/api/oauth2/api or api.patreon.com/oauth2/api ) will stop responding on October 7, 2026.
Facts
- API
- Patreon API
www.patreon.com - Kind
- Version retirement
- Announced
- August 7, 2026
- Takes effect
- October 7, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Patreon API's own pages
Questions
When does this change take effect?
Calls to /api/oauth2/api/* on Patreon API stopped working on October 7, 2026.
What happens to calls after October 7, 2026?
They have failed since October 7, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Patreon API 1
-
/v1/*Version retirement Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.