Mechanisms for automated access to (part of) the web API through bot accounts/tokens

As a developer on the Roblox platform, who specializes in creating websites, and services, I am always finding a reason that I need to be able to work with Roblox user accounts to perform automated-bot actions. I have a few reasons that have persuaded me to make this post.

I am always finding myself in a predicament of trying to find and fix API issues without having a native, supported bot API, and sometimes have to find new ways to solve captchas in real-time, which can be quite expensive, and at some points, unbearable for site developers like me.

For users, this makes it easier to differentiate a bot from a typical player; this also allows Roblox to have more control over what’s going on with bots on the platform. I can only assume how many bots there are on the Roblox platform that perform unnecessary requests because there is no documented API for developers outside of Roblox. Yes, every subdomain has documentation; however, they change, and you sometimes don’t know until it’s affecting your end-product.

Having no developer supported bot API is such an issue that people on the Roblox platform pay for people to host bots, and other services like that for them. There must be thousands of people who pay or use bots, which are just clogging up the normal user count. On another note, I know that there is considerable demand for bots, I know this because I own a service named myCenter – a service made around automation and applications that has over 5,000 groups joined on our platform in a matter of a few months. I’ve also seen a lot of other people creating services for the sole purpose of creating bots, which have hundreds of users.

Now with all great things comes with restrictions, this bot API should be limited, of course, actions such as liking games, messaging, and the following players should be disabled to prevent abuse.

54 Likes