Instagram Mobile Automation

stock69

Newbie
Joined
Jul 17, 2022
Messages
4
Reaction score
3
Hey, I'm currently building an Instagram automation thing. I've heard that mobile API calls are the best way to go when they actually work reliably.
I've got a real Android phone that's rooted, and I've successfully bypassed SSL pinning — so now I can intercept all the network traffic from the app.
How would you guys proceed from here? What's the next step? Should I automate stuff directly on the phone (like with UI automation) or reverse-engineer the mobile API requests and build my own backend service that sends those calls programmatically?
 
Hey, I'm currently building an Instagram automation thing. I've heard that mobile API calls are the best way to go when they actually work reliably.
I've got a real Android phone that's rooted, and I've successfully bypassed SSL pinning — so now I can intercept all the network traffic from the app.
How would you guys proceed from here? What's the next step? Should I automate stuff directly on the phone (like with UI automation) or reverse-engineer the mobile API requests and build my own backend service that sends those calls programmatically?
You should 100% automate on the phone but the issue is the api calls, no that is not the best way to go about it thats literally like the first sign to ig that you are a program running these automations lol
 
You should 100% automate on the phone but the issue is the api calls, no that is not the best way to go about it thats literally like the first sign to ig that you are a program running these automations lol
So you are talking about UI Automations?
Api mobile calls are definitely not the best nor Android is. Best is ios automation but that is hard so the ios automation is the best
Are we talking about Jailbroken Phones which run a specific automation software?
 
UI automation is relatively safe and stable, while direct mobile API reverse-engineering is more risky and is detected quickly. Make your decision keeping TOS and legal risks in mind.
 
Hey, I'm currently building an Instagram automation thing. I've heard that mobile API calls are the best way to go when they actually work reliably.
I've got a real Android phone that's rooted, and I've successfully bypassed SSL pinning — so now I can intercept all the network traffic from the app.
How would you guys proceed from here? What's the next step? Should I automate stuff directly on the phone (like with UI automation) or reverse-engineer the mobile API requests and build my own backend service that sends those calls programmatically?
Best way is to do mobile + API. Do your actions via mobile. Then sometimes you can use API. For example following/likes etc..
 
You should 100% automate on the phone but the issue is the api calls, no that is not the best way to go about it thats literally like the first sign to ig that you are a program running these automations lol
don't understand why people want to use api to be honest. what can you do that you cannot do with automation?
 
You can still use API calls, however for doing "Like" actions, the profile might get flagged. That being said, API is good for profiling the accounts.
 
If you want something that actually lasts, stick with automating on the real phone because it breaks less and looks more natural. Rebuilding the mobile API can scale better, but it’s risky and usually turns into constant maintenance when Instagram changes things.
I already have a real device farm but I also want to manage 100k+ profiles that need to survive only one day
 
From experience, UI automation on real devices is slower but far safer and more stable long term; deep API emulation breaks fast as Meta updates checks. If you care about longevity, prioritize human-like behavior and device consistency over clever reverse-engineering.
 
don't understand why people want to use api to be honest. what can you do that you cannot do with automation?
Simple, Quick and Huge scalling with less resources.
Let's suppose you want to run 10K accounts for IG, how would you do that without having thousands of devices?
Have you thought about the cost of setup for running 10K accounts vs running them throgh the API?
I'm not advocating for the API automation but what API automation offers isn't possible with UI automation with same cost or near cost.
 
Why not using automation on Cloud phones? That's what I do. And I put AI to overpass all the updates in a few hours.
 
The hard part isn't sending the request. It's keeping it working after Instagram changes something.
 
UI automation is ugly, but reverse API is worse when Instagram changes one small thing
 
Back
Top