You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 17, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 17, 2026. It is now read-only.
A big problem nowadays. Looks like instagram is improving their security algorithm day by day. They are somehow detection that we are using their API in unauthenticated way
To avoid these challenge, you can :-
Use cache instead of logging everytime
Add human interpreted gap between every request
Do not use new accounts. accounts which are not older then 90 days suffer this problem the most. Instagram keep tracks of new account.
A big problem nowadays. Looks like instagram is improving their security algorithm day by day. They are somehow detection that we are using their API in unauthenticated way
To avoid these challenge, you can :-
* Use cache instead of logging everytime
* Add human interpreted gap between every request
* Do not use new accounts. accounts which are not older then 90 days suffer this problem the most. Instagram keep tracks of new account.
I will update it as soon as I get the fix
Maybe we can avoid it by updating APP_VERSION in instagram4j IGConstants and using new IGAndroidDevice`s ???
A big problem nowadays. Looks like instagram is improving their security algorithm day by day. They are somehow detection that we are using their API in unauthenticated way
To avoid these challenge, you can :-
* Use cache instead of logging everytime
* Add human interpreted gap between every request
* Do not use new accounts. accounts which are not older then 90 days suffer this problem the most. Instagram keep tracks of new account.
I will update it as soon as I get the fix
Maybe we can avoid it by updating APP_VERSION in instagram4j IGConstants and using new IGAndroidDevice`s ???
Yeah, this is one of the crucial factor which is causing this problem. But instead of fixing that, we are again reverse engineering Instagram API with all the factors and constants taking in account. This one will be using Web API where as old instagran4j was using mobile version API.
So instead of contributing to instagram4j, you can contribute in making of this new API
Activity
spapapan commentedon Jan 16, 2023
It is worth noting that I got this error the second time I tried to make a request, so it's not that I spammed.
ErrorxCode commentedon Jan 17, 2023
A big problem nowadays. Looks like instagram is improving their security algorithm day by day. They are somehow detection that we are using their API in unauthenticated way
To avoid these challenge, you can :-
I will update it as soon as I get the fix
noirtier-villefort commentedon Aug 18, 2023
Maybe we can avoid it by updating APP_VERSION in instagram4j IGConstants and using new IGAndroidDevice`s ???
ErrorxCode commentedon Aug 27, 2023
Yeah, this is one of the crucial factor which is causing this problem. But instead of fixing that, we are again reverse engineering Instagram API with all the factors and constants taking in account. This one will be using Web API where as old instagran4j was using mobile version API.
So instead of contributing to instagram4j, you can contribute in making of this new API