IG Bot Registration - Hitting Repetitive Selfie Checkpoint Wall

[cryxos]

Hey BHW community,

I've been working for the last couple of weeks on a bot system for IG, using the "iam from Perfect Studio" tool to manage the process.

I'm focusing on the new registration flow, but I'm running into a consistent issue. Right after the initial API login, my accounts hit a checkpoint. This then leads to a repetitive loop where the account is asked for a CAPTCHA, then SMS verification, and ultimately a selfie verification. At the selfie stage, I obviously abandon the account.

I'm trying to figure out where the detection is happening and would appreciate some insights from the experts here.

My main questions are:

1. Does anyone have specific experience or data points on what triggers these escalating checkpoints via the API? How does the system detect and classify the risk right after login?
2. What are the current best practices in 2025 for increasing the overall longevity of accounts right from the start?
3. Are there any proven experts in this specific area here? I'm looking to connect with someone who has demonstrable and verifiable success in creating stable accounts through automation.

Thanks for any help or pointers you can provide!

 

[AspiringNomad]

Having had a little experience with iam, I can maybe shed some light on your question 1. First and foremost, two key things about iam:

1. iam's account registration module is hardly used by anyone because it hasn't been updated for a very long time. I would instead look at either buying accounts - aged ones work best - or search for dedicated ig account creator tools. Might be best though to start with just buying accounts and gain experience with iam first.
2. Meta detects and flags api activity easier than when using real devices, so automation tools using api will always carry a little more risk. I personally suspect that this is the main cause of the repetition of the flags in iam for the accounts.

Aside from that, there are simply too many factors for there to be a golden answer. But in general, some of the key ones:

• The account needs to connect from a trusted IP. If you're using proxy, mobile proxy has the highest trust score.
• The account's locale / country in which it was created should match the proxy's IP geography. So if you e.g. have an account with the US as locale that connects with IP from say Greece, that raises a flag.
• The activities on the account should be light, low-risk, and spaced out for an extended initial period.

You have to continuously test and refine to work out what works for you.

 

[cryxos]

Having had a little experience with iam, I can maybe shed some light on your question 1. First and foremost, two key things about iam:

1. iam's account registration module is hardly used by anyone because it hasn't been updated for a very long time. I would instead look at either buying accounts - aged ones work best - or search for dedicated ig account creator tools. Might be best though to start with just buying accounts and gain experience with iam first.
2. Meta detects and flags api activity easier than when using real devices, so automation tools using api will always carry a little more risk. I personally suspect that this is the main cause of the repetition of the flags in iam for the accounts.

Aside from that, there are simply too many factors for there to be a golden answer. But in general, some of the key ones:

• The account needs to connect from a trusted IP. If you're using proxy, mobile proxy has the highest trust score.
• The account's locale / country in which it was created should match the proxy's IP geography. So if you e.g. have an account with the US as locale that connects with IP from say Greece, that raises a flag.
• The activities on the account should be light, low-risk, and spaced out for an extended initial period.

You have to continuously test and refine to work out what works for you.

Can you recommend where to buy aged accounts?
And should they be from one country where even the proxy and phone number are from?

 

[teotheceo]

Avendo avuto un po' di esperienza con iam, posso forse fare un po' di luce sulla tua domanda 1. Prima di tutto, due cose fondamentali su iam:

1. Il modulo di registrazione account di IAM è praticamente inutilizzato perché non viene aggiornato da molto tempo. Personalmente, prenderei in considerazione l'acquisto di account (quelli vecchi sono i migliori) o la ricerca di strumenti dedicati alla creazione di account IG. Tuttavia, potrebbe essere meglio iniziare semplicemente acquistando account e acquisire esperienza con IAM.
2. Meta rileva e segnala l'attività dell'API più facilmente rispetto ai dispositivi reali, quindi gli strumenti di automazione che utilizzano le API comportano sempre un rischio leggermente maggiore. Personalmente, sospetto che questa sia la causa principale della ripetizione dei flag in IAM per gli account.

A parte questo, ci sono semplicemente troppi fattori perché ci sia una risposta univoca. Ma in generale, ecco alcuni dei più importanti:

• L'account deve connettersi da un IP attendibile. Se utilizzi un proxy, il proxy mobile ha il punteggio di attendibilità più alto.
• Le impostazioni locali/il Paese in cui è stato creato l'account devono corrispondere all'indirizzo IP geografico del proxy. Quindi, se ad esempio hai un account con l'indirizzo locale degli Stati Uniti che si connette con un IP, ad esempio, dalla Grecia, questo genera un problema.
• Le attività svolte sul conto devono essere leggere, a basso rischio e distribuite per un periodo iniziale prolungato.

Devi continuamente testare e perfezionare per scoprire cosa funziona per te.

Follow

 

[teotheceo]

Puoi consigliarmi dove acquistare conti scaduti?
E dovrebbero provenire dallo stesso Paese da cui provengono anche il proxy e il numero di telefono?

Follow