Getting Frequent 503 errors while testing the new friends API

While using the following API endpoint:
https://friends.roblox.com/v1/users/{user_id}/friends/find?limit=50&cursor={cursor}
which returns a paginated result of a user friends, I’m receiving a lot of 503: Service Unavailable errors. I’m currently making many API calls to that endpoint, however I consider the amount of 503 errors I receive a bit high(to the point where I have started ignoring them instead of printing them as errors).

I call the API programmatically by doing simple GET requests in a python script. The only header I bother setting is the user agent one, since Roblox seems to not need any CSRF or authentication tokens for this endpoint.

Expected behavior

In case this is due to spamming or a similar error, I must receive a client sided status code(4xx) instead of a server side one(5xx). I am already managing the amount of requests I make by yielding my script when it receives a 429(rate limit) status code.

Is there any reason you’re using /friends/find instead of just:

https://friends.roblox.com/v1/users/8247889676/friends ← To get a list of all friends

Not sure if this will help fix your issue but it could reduce the amount of requests you’re sending.

Yes, it has less strict rate limits, and it also works for users with more than 200 friends(by paginating with cursors).