@hwup might be quicker to answer questions related to the 429 change, I'm currently only maintaining this wrapper, not using it much myself. Reason for the mentioned change was issue #344. I think that instead of having a freeze, a request returning 429 is now throwing an exception. @hwup could you confirm or give insight into the other questions if you've been using the code recently?

I've added the missing release notes now.

Just happened to get "Too Many Requests" exception only on Get Playlists starting yesterday; fine on all others. Worked perfectly fine before. Also had the freeze previously, but updated to v8.3.0, and that seemed to fix it, but it was replaced with 429.

Previously when it encountered 429, it would sleep for amount of Retry-After header, so you would not notice when you would get 429 and it was a short wait, in case it's a long wait, you would notice because it would "hang". After the PR #345, now it throws exception and you can choose what to do. You can use getRetryAfter in ToomanyRequestsException and sleep, etc.

Spotify docs mention a header Retry-After which should give value in seconds for a pause before a next request. Is this implemented here? In general, how to access headers using this API? Thanks.

spotify-web-api-java/src/main/java/se/michaelthelin/spotify/exceptions/detailed/TooManyRequestsException.java

Lines 8 to 11 in 0799b42

	public class TooManyRequestsException extends SpotifyWebApiException {
	private int retryAfter;