Summary

Looks like your API has a knack for hitting rate limits with a whopping 553 occurrences of that issue. Also, a lonely trailing slash on the server that just wants to be part of the team with 1 occurrence.