#api.roblox.com replacement
1 messages · Page 1 of 1 (latest)
erm yes i think
1 sec
okay thanks
yea
isn’t it a post request instead of get too
erm
i cant recall
i remember reading the docs and there was like 1 end point saying something something its a post but actually a get because rate limit
but idk
well u can do that
but there's one to get em by userid too
this didn't allow an array?
i assumed it did just by doing ?username=?username=
yeah i know
i meant before it was removed
also i dont think it's deprecated i'm pretty sure it doesn't even work anymore at all
Use this endpoint: https://users.roblox.com/v1/usernames/users
Unfortunately does not support GET requests. So you'll need to add some extra code to get a CSRF token and make the post request
@dense geode
Actually, this endpoint works with GET requests "https://users.roblox.com/v1/users/search?keyword={username}&limit=10" but it returns 10 results, so you'll need to add some logic to find which one matches your username exactly
Honestly, I recommend using the first one with a POST request, it's a neater way of doing things
it accepts 100
aswell
and u can use the nextPageCursor to get the next 100 too :d
Lol, are you trying to find just one user or trying to get a list of users?
I thought you jsut wanted a specific one
i'm not trying to do anything
Oh oops that's right. Headless wanted it, mb
^ this was solved already
@silk pike also the POST one u provided
i'm pretty sure it only accepts 100
usernames aswell
Hm, it's not marked as solved
oh yeah
no, one returns 100, and the other allows you to submit 100
the GET returns 100 if you want that
the POST allows you to submit up to 100
i guess if u want a od number u use the POST one
@silk pike turns out u dont even need the csrf token
for the post endpoint
This endpoint will also check previous usernames.
Does not require X-CSRF-Token protection because this is essentially a get request but as a POST to avoid URI limits.
so the post is def better