Instagram private API TypeScript SDK for NodeJS runtime

IGPAPI is a powerful and feature-rich SDK for Instagram Private API built to provide developers with a reliable and easy-to-use solution for accessing Instagram's functionalities. This API is designed to be straightforward and efficient, enabling seamless integration with your applications.

You can contact me in telegram or email for details.


This documentation is intended for a high-level introduction to the capabilities and functionality of IGPAPI. If you're watching at this extensive list of classes and interfaces and feel overwhelmed, don't worry. In reality, it's not as complicated as it may seem. As you explore IGPAPI, I am here to personally assist you in overcoming any integration challenges and to clarify the relationships between modules and their interactions.


  • Comprehensive coverage of Instagram functionalities
  • Up-to-date and stable API implementation
  • Personal support for integration
  • Responsive to feature requests and bug reports

Frequently Asked Questions

Will I be able to make more actions (like/follow/comment/DMs) with IGPAPI?

IGPAPI is the most up-to-date API Client, but it is not a magic solution. If you plan to use it for abusive purposes, it's up to you to develop the right strategy. Each spammer has their own approach to avoid blocks and make more actions. Most of our clients are not spammers. They use IGPAPI to build auto-posting services, direct messaging bots, extended live-streaming and other applications. IGPAPI will help you to cater to various purposes.

Do I get access to the full source code with the monthly license? With the monthly license, you will have access to the majority of the source code. The IGPAPI project is a monorepo with several NPM packages. You will receive the source code for all packages, with the exception of the @igpapi/core module. This specific module, which represents about 2% of the entire source code, contains low-level framework logic and license-checking that is not directly related to Instagram. However, you will be able to expand and modify the source code as needed, giving you substantial control and flexibility.
Is it backward-compatible with V1?

Unfortunately, we were not able to maintain backward compatibility. However, there isn't too much code to refactor on your end. The main incompatibility lies in the ig.state section. You'll need to refactor this part of your code. By the way, state management is an area where the new library truly excels. Other components (repositories, services, entities) retain the familiar interface.