/cloud/v2/groups/{group_id}/memberships/{membership_id} will return a non-descriptive error “The request was invalid” if you provide invalid arguments, the user is not in the group, the user is already the same rank, or the user who created the API key does not have permissions to update the user’s rank to the provided rank. A separate error for each of these cases can help developers debug why requests are failing and provide accurate error messages to their users without adding overhead and performing these checks themselves. This was the case on the legacy endpoint, but is not on the Open Cloud version for some reason.
Today, I switched from using the cookie-authenticated groups.roblox.com API to the new apis.roblox.com one for group ranking in order to try and fix an issue. Sadly, the issue we are experiencing was not fixed.
Seemingly for no reason, requests result into a 500 error or a 400 error. The only information we get is “The request is invalid (HTTP 400)” or “Exception was thrown by handler (HTTP 500)”. All requests we send to Roblox are valid, and work when requested again the exact same way.
The previous API on groups.roblox.com suggests that whatever server I am being connected to is not aware that the member I am attempting to rank is part of the group:
We do not allow players to do an application if they are not in the group. We have also checked the membership of some members that had a failed ranking request, and they were still ranked as “Valued Customer” within the group.
The APIS also return invalid status codes that do not correctly specify what was wrong with the request. Such as 400, the request wasn’t bad, however that the request could not be processed for some reason. Or if someone who has already been ranked and you try to rank them to the same role, it also gives 400, when it should be returning something like 409.
