Quick Poll For FULL API Users

Instagram Marketing
#1

API users only

Hey guys just wanted to ask for you guys on full API - when you get an action block what do you do? Switching over from EB Only and seems API+contextual is working but have 2 accounts now with an action block during warmup

Many thanks!

  • Leave it alone - It will eventually follow in a few hours and figure itself out
  • Pause Account for 24 hrs, then restart in API, lower warm up settings
  • Pause Account for 48 hrs, then restart in API, lower warm up settings
  • Switch to EB Only and see if that works, if doesnt, rest for 24hrs

0 voters

1 Like
#2

I’m asking myself the same question.

At the moment I’m running with ONLY EB with almost no blocks.
But I want to run few test accounts on API Full Emulation as well.

Most of the blocks are session blocks in my experience.
Are they going away by itself on API Full Emulation?

When I get them on EB I could wait 2-3 days but the session blocks will still be there until I did a Logout/Login.

1 Like
#3

Roy hope ur doing well

I’ve switched 80% of mine to API and its working much better than a few months ago. I posted this thread to solve the other 20% of my accounts. These were working fine with API but recently run into the action blocks. I find the following:

80% - changed to API no blocks at all, reaching over 100 actions after warmup soon
20% - changed to API no blocks for first few days during warmup, now I am getting action blocks. I switched over to EB and some continue on, while others are getting temp blocks. May have to rest those that are getting blocks with API or EB.

I recall when I was only on EB - I had to relogin etc as well… but after awhile id get AC message for relogin too much. So I switched over back to API

#4

You did not mention scrappers, please note that the scrappers are very essential when it comes to blocks.

They are reducing the number of API calls made from the main account to the min, so if you are not using them you should definitely do.

1 Like
#5

All accounts using scrappers. 1 4g proxy to 5 accounts. Just got a hard block on a API one so adding more intervals into it now and see…

Sucks it was running smooth but seems like it doesnt last?

#6

Hey there,
Actually my answer is not listed above,
I’m running 20 accounts on Full API.
Whenever I see a block, I do a reloging and start actions.
95% of times, accounts do all the configured actions.
If the account gets another block, I leave it for 24hrs,

Only doing Following/Unfollowing. + Posting (1 Post per day)

I’m growing these accounts for a client and they are new accounts.
Aged accounts, purchased from reputed sellers on this forum.
All accounts are running on 4G Proxies. 8-10 accounts per Proxy.

For me, API works the best than EB.

2 Likes
#7

Thanks

You said “Whenever I see a block, I do a reloging and start actions.”
For API on action block:
Do you just go to profiles - Ig actions - relogin accounts, then click follow again?

Of course hard block - just have to pause and wait it out…

Is this correct? thanks!

#8

Yup. That is what I do.
Keep in mind, I only do this ONCE PER DAY. :smiley:

1 Like
#9

Got it thanks! Will give this a try…

I’ve been switching to EB once API gets blocked, and it runs again… But EB always gets temp blocks later on and need to relogin+follow which is bad.

Seems API is working better for me too, results are mores stable and can almost get to 100 follows/day… EB shuts down around 30-50 range

1 Like
#10

Yeah, for some EB works the best and for some API.
Good Luck

1 Like
#11

That’s going to lead to you getting account compromised messages after too many. It was once an option, and they removed it due to that.

1 Like
#12

I meant EB only. I switch the entire account work in EB only.
I dont do the auto switch to EB - yes AC for sure

#13

When I tried running actions in eb, for some reason it wasnt using contextual follows, so I’ve moved on to full api w/ emulation, and residential proxies. It’s been running good so far.

1 Like
#14

Eb only for me was working contextual but always get temp blocks. Ive moved to API as well.

But I did update settings so that might be why as well

#15

the first thing I do when I get action blocked is Re-login account, then restart the tool with lower settings. If the block is still there I stop the account for 24 hours. I don’t want to risk it getting HB.

if after 24 hours the block doesn’t go away, I switch to using the EB.

1 Like
#16

Relogging in once you get a temp block will eventually lead to compromised accounts… they removed that option from jarvee due to that. I would limit it to max 2 a day if you choose to continue that method.

#17

Found this to work hopefully this helps others:
API only with scrapers.

Low warm up settings, let it run. If you can action blocked:

  1. Leave it alone and see if it will figure itself out after suspension/delay time of a few hours
  2. If still stuck, relogin API, then run follow tool (only relogin once a day)
    3a) If it runs, then its ok, turn down settings a bit
    3b) If it doesnt run, turn off actions and rest for 24hrs and start from 1 again
    3c) Change all settings to EB Only, stop tool, relogin with EB, then run in EB - if it works then run in EB if blocked then rest for 24hrs

Thanks @nm9013 @Klique @roy @ossi

2 Likes