[joostlek]

Proposed Changes

SpotifyRateLimitError and SpotifyAuthenticationFailedError are exported but never raised, and the rate_limit.json fixture isn't used by any test. A 429 or 401 response was returned as if it were data, then failed in the models with a confusing MissingField error. This is the behaviour #417 reported; the fix from #425 appears to have been lost.

_request now raises:

• SpotifyAuthenticationFailedError on 401
• SpotifyRateLimitError on 429
• SpotifyNotFoundError on a 404 status code, in addition to the existing check for a 404 error body

New tests cover all three; they fail on main and pass with this change.

Related Issues

• Regression of Playback State improperly loaded in limited api access condition #417 (fixed in Raise exception when rate limit exceeded #425)
• Reference: https://developer.spotify.com/documentation/web-api/concepts/api-calls#response-status-codes

---

Generated by Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud