So basically I’m looking to make a group payout within Roblox Studio using the http method. I know the basics of JavaScript and I’m still learning it, but I’ve faced some issues. I fixed most of them, but the thing I’m currently struggling with is:
I followed the steps from this post in order to achieve the goal. However, when I try to get a “challengeId” in order to get a verification token for the 2fa verification requirement, nothing happens. Every time I make a request to https://groups.roblox.com/v1/groups/{GROUPID}/payouts in order to get a new challenge id, its a different than the previous one, and when I input one of those in https://twostepverification.roblox.com/v1/users/{USERID}/challenges/authenticator/verify, it says “Invalid challenge ID”. I don’t have problems so far with the authentification code, but I don’t know what else to try.
The challengeId from https://groups.roblox.com/v1/groups/{GROUPID}/payouts is different each time, because when making a request to that endpoint, its a different request each time, so roblox makes a new challege for that request. You have to save that challengeId and use it later in the code.
Okay, I get it. However, my issue is that every time I use that challengeId and input it in the verify url http request, it returns the same error “Invalid challenge ID”. Maybe the verification code is wrong or something, but its always that error.
Btw, I forgot to mention that I’m not making all of this with code. As I mentioned before, I just know the basics of JavaScript, so I go directly to the groups documentation and test it out there. I don’t know if it’s relevant, but I point it our just in case.
Hey, its been a while. I’ve been playing around with this, but I got a new error. When I try to make a POST request to https://twostepverification.roblox.com/v1/users/{USERID}challenges/authenticator/verify, it pops the error code 0 “Token Validation Failed”. Any ideas on how to fix this? I think it’s something about the cookie or the x-csrf-token thingy, but I input that correctly in the headers.