Looking for a Instagram bot that works outside the Instagram API.

Joined
Sep 18, 2013
Messages
438
Reaction score
335
Hello i've searched around the forum and i've not found what i am looking for so..
Anyways i'm looking for a bot (if there is any) that works outside of the Instagram API so i'll be able to like pictures every 1-3 seconds and so on.
If that is possible then send me a PM or write in the thread :)
 
Outside of the API lol? How should that work. How should the bot communicate with the server?
 
Yeah but eventually everything goes through their api. Either their public one or the private one that is used on phones
 
I'm not that much into Instagram but i remember a while ago that i used a bot where i got like mass amount of pictures in a short period of time.
 
Yea, IG is to old for a hack like this to work and work well. You have to go through their API in someway shape or form.
 
Yeah but eventually everything goes through their api. Either their public one or the private one that is used on phones

Yup you nailed that one down. People instagram is really not what it used to be. FB has cracked down on their api and update all the time. A not of that nature could run you $1000+ for Dev access
 
The only way to do those type of actions is through the API, I've written instagram bots. They have made it essentially impossible as they are now checking IP addresses tied to accounts so that rules out proxies, if you login to an account from different IP's they will lock the account out. Like jimmylegs said they have really tightened things up.
 
I got a script that works in Firefox. It does LIKES ONLY!!! But it works, is easy to use and customize which tags you want it to target. It uses web.stagram.

I just wake up in the morning, press play and it spends the next 12 hours liking photos. 35-45 seconds between each like. Randomized to avoid pattern detection. It likes 1k photos per day... you can change it, but you don't want to be too aggressive bc you'll get banned that way.

The script was cheap and she showed me how to use it.
 
I got a script that works in Firefox. It does LIKES ONLY!!! But it works, is easy to use and customize which tags you want it to target. It uses web.stagram.

I just wake up in the morning, press play and it spends the next 12 hours liking photos. 35-45 seconds between each like. Randomized to avoid pattern detection. It likes 1k photos per day... you can change it, but you don't want to be too aggressive bc you'll get banned that way.

The script was cheap and she showed me how to use it.

How can I get that script?
 
lol at all the people saying this can't be done. What OP means is access to the private API (so it looks like the requests are coming from a phone). Once you can do this you have to use 1 acocunt per proxy and never change it. Also you need aged accounts. Its a tough battle with IG nowadays but once you figure it all out its totally worth it.
 
lol at all the people saying this can't be done. What OP means is access to the private API (so it looks like the requests are coming from a phone). Once you can do this you have to use 1 acocunt per proxy and never change it. Also you need aged accounts. Its a tough battle with IG nowadays but once you figure it all out its totally worth it.

lol at the guy that thinks he knows something no one else does. The OP clearly said a bot outside of Instagrams API even if you're using their mobile API...........it's still their API, it still has strict limits. And btw you can use more than 1 account per proxy on their mobile API as long as you don't run over their limits.
 
http://stackoverflow.com/questions/1598407/iphone-and-wireshark

If anybody wants to create one of these things, this is a good place to start. I'd be curious to see what the real limits are like.

On a side note you can't really assume the app is using something like the public API, or an API at all. A client/server application or web app will generally make calls that are optimized for very specific pieces of functionality in the software. You're generally looking for efficiency so you're not going to deploy an API then build on that. An API is a whole separate thing where it's designed to provide the broadest possible range of functionality at the expense of efficiency.

Then again it could actually be calling something really close to the public API, but you'd have to do the work to actually confirm that.
 
Last edited:
Back
Top