OAuth scopes removed without notice broke all token refreshes in production #1689
Unanswered
cervinakuy
asked this question in
Q&A
Replies: 1 comment
|
Thank you for reporting this issue. The refresh failures for integrations still requesting the older scope set were not intended, and that issue has> Thank you for your continued support and use of our API. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Confirmation
Question / discussion
What Happened
Today (2026-08-12) at approximately 14:54 UTC, our OAuth token refreshes began failing. The cause was that eight scopes we had previously been granted are no longer returned:
Root Cause
These appear to have been removed from the API entirely.
components.securitySchemes.oauth2in the official API (and the generated spec) now defines only 12 scopes, and searching the full document returns zero occurrences of any of the eight.The change took effect mid-flight: our scheduled refresh at 14:09 UTC succeeded and the next one at 14:54 UTC failed, with no deploy on our side in between.
Because our client still requested the previous 20-scope set, the narrower scope in the refresh response triggered a blocking scope-change error. That meant every refresh failed, including the scheduled job whose only responsibility is renewing the token; so once the access token expired all our backend workers lost all Etsy API access for roughly two hours.
The Impact: Customer orders went unprocessed during that 2 hour window.
Our Fix
We use
oauthlibin Python, and our immediate short-term fix was setting OAUTHLIB_RELAX_TOKEN_SCOPE (this is not set by default). We've since trimmed our requested scopes to the 12 currently defined, which is also another fix option.Our Requests (on behalf of the Etsy Developer Community)
We kindly have two requests:
Please announce OAuth scope removals in advance. A short note on here beforehand would have let us adjust our requested scopes ahead of the change rather than diagnosing it mid-outage. Scope removals are unusual among breaking changes in that they can break authentication itself, so even working integrations that never call the affected endpoints go down.
The authentication guide at https://developer.etsy.com/documentation/essentials/authentication still lists all 20 scopes, including the eight removed. It contradicts the API spec / generated spec, which made this much harder to identify. We initially ruled out a scope change because of that page.
Happy to provide more detail if it's useful.
Kind regards,
Cervinakuy
All reactions