Summary

Looks like your API is playing a game of "Who's Got the Most Issues?" with a whopping 206 occurrences of defining error responses for status code 500. Additionally, it seems to have a flair for drama with 220 instances of rate-limiting responses.