Complete Response Codes in Twitch Docs
It would be great if we could have a list of the status codes and their reasons so we can write code to prepare for handling those errors, instead of logging them and dealing with them as they happen - for all endpoints. These exist, for the most part, in a lot of the newer endpoint documentation, but a lot of the older endpoints were rushed in their documentation and we have little information on what responses to expect. Sometimes we get 200s, 202s, 400s, 410s - and having to just "wait" or try to plan for them is a big frustrating. We have these Response Codes for less than 10% of the endpoints that exist in Helix (4/50)
2
votes
BrandinArsenault
shared this idea