@igpapi *@2.x.x description

We are glad to announce the next 2.x.x version of this library. It's a big release. We have significantly expanded the functionality and capabilities. The library turned into a monorepository and now it's a set of libraries, connected in an ecosystem:

package name	description
@igpapi/android	Basically it's just an improved up-to-date version of the public instagram-private-api.
@igpapi/web	API client for web Instagram application (https://www.instagram.com).
@igpapi/android-realtime	Brings all the android realtime stuff to your code. Yes, you can subscribe to new messages.
@igpapi/web-mqtt	Brings all the web realtime stuff to your code.
@igpapi/chrome	NEW! Headless browser automation. Likes, follows, etc
@igpapi/sticker	Just a sticker constructor for the stories.

You can share one session between all these libraries. For example, you can log in with @igpapi/android, and pass this session to any other library, it will work. The weird challenge behavior problem is solved: all challenges completes successfully.

F.A.Q.

How to see the full feature list?

Open the Instagram app on your IOS/Android phone and watch the abilities. We support most of them. I can't publish the full feature list, because it would be very big. There are a lot of functions. So please, don't ask me about it. Better ask me if it supports the feature you need.

What's with action blocks?

We are selling only up-to-date API Client, but not a magic pill. If you want to use it for spam - it’s up to you how to cook it right. Every spammer has got his own strategy to avoid blocks. Most of our clients are not spammers. Someone builds auto-posting service, someone direct-bot. Someone spamming. We got an SDK for all these purposes.

Is it SaaS?

No, it communicates directly with Instagram servers, without any middle-layer.

Is it backward-compatible with V1?

Unfortunately, we were not able to save backward compatibility. But there is not too much code to refactor for you. The main incompatibility is in `ig.state`. You'll just need to refactor this part of your code. BTW state management is the place where the new lib really shines. Everything other (repositories, services, entities) remains with the good old interface.