Jump to content

(Platinum V VIP Player) API worked for a year now Error 1020


Featured Comment

I have had successful API calls for a year. Now in the last 2 days keeps coming back  code 1020. I know this is a cloudfront error for access denied. Is anyone else getting this error now?

I am a Platinum V VIP player and enjoy stake but am starting to look for alternatives which i would hate to do but this is forcing me to move away.

Link to comment
Share on other sites

25 minutes ago, yulius99 said:

im also error, just wait until fixed..

Thanks for reply... however I'm not a huge waiter. anyone find a solution?

4 minutes ago, AdamBetsMax said:

what does this API do exactly?

API is a way of interaction with stake.com services in a Headless environment. If that sounds like jiberish probably not a good idea to look into it further.

Link to comment
Share on other sites

Posted (edited)
7 minutes ago, dupeddonk said:

Are you including all the same headers that a bet through your browser includes?

I have been using the api for over a year and my headers have been fine.

In the interest of being complete here are my headers. Witch i have never had any issues with.

 

{

            "Content-Type": "application/json",

            'User-Agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36',

            "Content-Length": payloadStr.length,

            "x-language": "en",

            "x-access-token": exports.token

        }

Edited by Digighost
Completeness
Link to comment
Share on other sites

34 minutes ago, Digighost said:

I have been using the api for over a year and my headers have been fine.

In the interest of being complete here are my headers. Witch i have never had any issues with.

 

{

            "Content-Type": "application/json",

            'User-Agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36',

            "Content-Length": payloadStr.length,

            "x-language": "en",

            "x-access-token": exports.token

        }

I can't test it with any scripts right now, but I'm able to make single bets through the console with simple fetch requests.

My guess is cloudflare is throwing error because it knows you are making request from somewhere besides the browser.

 

You could try adding these headers:

     "accept": "*/*",

    "sec-fetch-dest": "empty",
    "sec-fetch-mode": "cors",
    "sec-fetch-site": "same-site",

 

You might also need to add:

"mode": "cors",

after

"method": "POST", 

 

If it's not there already.

Link to comment
Share on other sites

1 hour ago, dupeddonk said:

I can't test it with any scripts right now, but I'm able to make single bets through the console with simple fetch requests.

My guess is cloudflare is throwing error because it knows you are making request from somewhere besides the browser.

 

You could try adding these headers:

     "accept": "*/*",

    "sec-fetch-dest": "empty",
    "sec-fetch-mode": "cors",
    "sec-fetch-site": "same-site",

 

You might also need to add:

"mode": "cors",

after

"method": "POST", 

 

If it's not there already.

Thanks for trying @dupeddonk but, unfortunately that didn't work.

Link to comment
Share on other sites

  • 1 month later...
3 minutes ago, Keibow said:

I am troubled. . . The API response has changed from 1020. Returns the HTML page source. The title is "Action required". What should I do?

Can you show request? I still have 403 error

Link to comment
Share on other sites

I get this answer from support:

Quote

Hi there.

API is currently down, and our team is working on building something new in the coming weeks that will serve as a replacement.

So I'm afraid that you won't be able to use any custom bots or other methods that might have been possible before.

This was a security change that we were sadly forced to undertake in order to better protect the integrity of our platform.

Kind regards.

 

Link to comment
Share on other sites

The API is not down. It is working fine just as usual. They can not take it down at all. The website itself uses the API. 

Stake Support has no idea.

 

stake_req.thumb.jpg.6e1ff48bfa5879d28605bc90bd8aee99.jpg

stake_req_2.thumb.jpg.02ec22ac9342497c93c491fe2c35b8e1.jpg

 

The 1020 error mentioned above is returned as result of IP rate limiting 🙄

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...