Intermittently getting ‘Invalid authorization code’ requesting an Access Token today, though above info suggests changes are now permanent and the API settled. This happens both locally and on AWS Lambda.
Combined with the poor messaging given by the API I’m very frustrated with Twitch.
As a maintainer of an open source authentication library I dislike having to work to support specific providers because they don’t behave like other popular services; it’s made worse when the error handling isn’t helpful.
For example, the Google oAuth service links to relevant documentation from errors when there are changes to the API.
While the documentation is extensive, I have not found it all that helpful as pages are missing important information (which is sometimes on another page and sometimes undocumented except in an old forum post and you are left to wonder if it still applies to the current version of the API).
Being inconsistent with version naming and endpoints is also not ideal.