Whether or not you can bypass the captcha request is a make or break feature when it comes to bots nowadays. If that's not possible, it must be a requirement to get as many "1-click" no-captcha requests as possible.
This thread will be used to discuss any-and-all strategies toward coming up with a way of either bypassing/getting as many 1-clicks as possible.
You'll notice a common theme here: 6LeoeSkTAAAAAA9rkZs5oS82l69OEYjKRZAiKdaF. From here on out, this will be referred to as the site_key, which by the name you might guess… is site specific.
The last two of the endpoints are the ones we want to really worry about. In order for Google to give us an approval rating, the request will contain data collected from: mouse movements, clicks, drags, and other events (see: this) in a base-64 encoded string.
Here's an example request to the given endpoint from the URL posted above:
Whether or not you can bypass the captcha request is a make or break feature when it comes to bots nowadays. If that's not possible, it must be a requirement to get as many "1-click" no-captcha requests as possible.
This thread will be used to discuss any-and-all strategies toward coming up with a way of either bypassing/getting as many 1-clicks as possible.
All the information below is specific to https://blendsus.com
Endpoints
Using Charles, I was able to find the endpoints for the captcha request & response.
You'll notice a common theme here:
6LeoeSkTAAAAAA9rkZs5oS82l69OEYjKRZAiKdaF
. From here on out, this will be referred to as thesite_key
, which by the name you might guess… is site specific.The last two of the endpoints are the ones we want to really worry about. In order for Google to give us an approval rating, the request will contain data collected from: mouse movements, clicks, drags, and other events (see: this) in a base-64 encoded string.
Here's an example request to the given endpoint from the URL posted above:
Which returns a valid response:
[ ... ] adding more later!