Whether this is an intentional choice is beyond me, since why would you have the SEND button if you don’t have the authenticated user. The other docs pages on the APIs themselves have your token, which makes the request valid
This also confuses me in where it sends the request from, since the base request itself through a URL would return a valid GET request, and not an error.
While we’re on this topic the consolidated page isn’t up to date either, so I would recommend just using the respective API pages found on this github.
I tried to generate an auth ticket for myself on the docs page but it looks like the request was never sent, no idea why.
I double checked for you and you are correct, the send button only sends 1 crafted request with our input to the endpoint, it does not attempt to actually get an auth ticket. I am guessing Roblox never implemented the logic to request for an auth ticket and then use said auth ticket in the request to the endpoints that needs it.
You can probably still test this endpoint yourself by writing something in js and running it on your browser. Request an authticket from one of those endpoints and then use it on the api you want to hit.
I am in the process of checking over bug reports and following up on some bugs that haven’t received any activity in a while.
Is this issue still occurring or can you confirm that this bug has been resolved? We are having a hard time reproducing this issue
