Instagram Api Account creation fails

Yeah there is no 50 log requests before, nor any "special token" and specially not one that is worth 200k usd. Every bot you make always requires maintenance on big sites, even on the lesser efficient web versions as selectors frequently gets updated due to element changes.
I made an API creator both for Android and iPhone a couple months back but the principle should remain the same so if you need any help let me know over PM and we can discuss.
It's also true they removed the request signing recently.
SO your account creation bot is working fine now?
 
Yeah there is no 50 log requests before, nor any "special token" and specially not one that is worth 200k usd. Every bot you make always requires maintenance on big sites, even on the lesser efficient web versions as selectors frequently gets updated due to element changes.
I made an API creator both for Android and iPhone a couple months back but the principle should remain the same so if you need any help let me know over PM and we can discuss.
It's also true they removed the request signing recently.

There really is, you should definitely look into some of the tokens sent and you'll find you might need to reverse Google apps (nearly impossible) in order to access it.

People have offered over $200k for this token and many devs do not give it out.

Hence why you see Chinese bot farms that flash/reset ROMS and restart creation process, because real phones can generate this token, but not API creators.

Creation is a points game. The more points you accumulate, the better. When you go over the minimum cap, the algorithm lets you create an account. Many of these tokens are worth a lot of points. Get ready for low success rates and constant purges if you can't generate some of these tokens.

By logging requests I mean footprints that you as a user leave behind with your IG app. Maybe there isn't 50, but there is a lot of them, and some of them are not accessible by typical reversing means (cert pinning), but are much harder to access.
 
Bullshit. Have you ever actually looked into requests the Instagram app sends on ios or Android yourself? There is definitely no secret token before the create request.
There are 2-5 logging client event requests before the create request. I did a test and blocked them on my phone and account creation always fails. Some days ago it still worked without it. These logging events mainly send timestamps. After the account creation there are some more complicated logging requests, however I don't care much about them, since I only need throw away accounts for scrapping. So it's enough to figure out how to simulate the initial 2-5 logging requests.
 
Bullshit. Have you ever actually looked into requests the Instagram app sends on ios or Android yourself? There is definitely no secret token before the create request.
There are 2-5 logging client event requests before the create request. I did a test and blocked them on my phone and account creation always fails. Some days ago it still worked without it. These logging events mainly send timestamps. After the account creation there are some more complicated logging requests, however I don't care much about them, since I only need throw away accounts for scrapping. So it's enough to figure out how to simulate the initial 2-5 logging requests.

+1
 
There really is, you should definitely look into some of the tokens sent and you'll find you might need to reverse Google apps (nearly impossible) in order to access it.

People have offered over $200k for this token and many devs do not give it out.

Hence why you see Chinese bot farms that flash/reset ROMS and restart creation process, because real phones can generate this token, but not API creators.

Creation is a points game. The more points you accumulate, the better. When you go over the minimum cap, the algorithm lets you create an account. Many of these tokens are worth a lot of points. Get ready for low success rates and constant purges if you can't generate some of these tokens.

By logging requests I mean footprints that you as a user leave behind with your IG app. Maybe there isn't 50, but there is a lot of them, and some of them are not accessible by typical reversing means (cert pinning), but are much harder to access.

Keep looking ;)



Good, you shouldn't use these accounts for anything else.
After you spoke about that token I checked the data in every single request, and there is just none. At least not on iOS didn't check on Android though.
 
I've also been trying to figure this out, I've emulated pretty much most requests except logging such as registering the device ID and getting attributes from it. Creation still fails, it's very obvious that the data sent is used to build up a profile, they have very well trained machine learning so all the logging sends things about the device e.g sim state, time, OS api version, advertising ID etc etc. Without these requests it will 100% fail creation. If anybody is willing to help me work out what needs to be changed please add my telegram: cto88 and we can try and figure it out. There's normally 4-5 logging requests, each containing different data that would be quite hard but not impossible to replicate, ranging from just the device properties and OS version all the way down to hardware logging such as sim state and carrier info.
 
There really is, you should definitely look into some of the tokens sent and you'll find you might need to reverse Google apps (nearly impossible) in order to access it.

People have offered over $200k for this token and many devs do not give it out.

Hence why you see Chinese bot farms that flash/reset ROMS and restart creation process, because real phones can generate this token, but not API creators.

Creation is a points game. The more points you accumulate, the better. When you go over the minimum cap, the algorithm lets you create an account. Many of these tokens are worth a lot of points. Get ready for low success rates and constant purges if you can't generate some of these tokens.

By logging requests I mean footprints that you as a user leave behind with your IG app. Maybe there isn't 50, but there is a lot of them, and some of them are not accessible by typical reversing means (cert pinning), but are much harder to access.
What's the tokens name then?
The only token I know of that is generated is the FCM which is used for notifications on an app. This one is not a deal breaker as no permission to notification means no token. Even I can generate these.
 
What's the tokens name then?
The only token I know of that is generated is the FCM which is used for notifications on an app. This one is not a deal breaker as no permission to notification means no token. Even I can generate these.
There is a token on one of the logging client events called an access token, but it does not appear to change, maybe he is referring to this?
 
Last edited by a moderator:
There is a token on one of the logging client events called an access token, but it does not appear to change, maybe he is referring to this?
Yeah, this is the outh2 token to access the Instagram graph API. There is one for the webapplication, one for the android app and one for the ios app. It doesn't change within those platforms.
 
There is a token on one of the logging client events called an access token, but it does not appear to change, maybe he is referring to this?
No that's not it and it's not related to Google directly. as @Zapdron mentioned in his post,

Yeah, this is the outh2 token to access the Instagram graph API. There is one for the webapplication, one for the android app and one for the ios app. It doesn't change within those platforms.

This token is used to authenticate a user to a platform. And as he mentioned each platform has a unique token. These tokens are for permission and identification.
it's commonly used in API-based applications (phone apps) such as Twitter, FB, Instagram, LinkedIn and it's supposed to be a lightway way of authentication where cookies are not used.
 
Unless you send the 50 logging requests that go before the create request that track user movement & hack one of the tokens that people pay up to $200k for, then be prepared to loose your API creator to updates. API creators are tricky.
hey bro im looking for a lot of instgram accounts could you please point me to it or teach me how to create a lot off accs i already know bout proxies just need a creation app
 
100% success rate is pretty neat. Were you using 4G mobile proxies for this method? Curious
If you're suddenly not being able to create accounts through API requests, either you've sent too many requests or IG detected something strange about your proxy.
 
Back
Top