Instagram private API TypeScript SDK for Node.js.
Contact me on Telegram or by email for access and integration support.
@igpapi/android — Android runtime@igpapi/ios — iOS runtime@igpapi/core — core types, HTTP infrastructure, errors@igpapi/pigeon-nest — telemetry layerPick @igpapi/android or @igpapi/ios depending on which client you want to mimic, install, and go. See the package README for quick start.
This documentation lists every exported class, function, and type across four packages — that looks like a lot. In practice, day-to-day use is mostly facade calls: ig.users.*, ig.friendships.*, ig.account.*, and so on. The low-level pieces are there for advanced scenarios.
If you hit integration snags or can't find the right call for your use case, reach out — I'll help you through it.
IGPAPI is an up-to-date API client, not an anti-ban solution. It handles the low-level stuff (device signals, signatures, sessions, telemetry) but account survival under heavy automation depends on your own strategy — pacing, proxy rotation, warm-up, content patterns. Most clients build posting tools, DM bots, live-streaming setups, analytics — not spam. If you plan to push hard, you're responsible for not getting your accounts killed.
Yes — monthly license gives access to the private repo with full source for every package. The published npm builds are obfuscated (license checker and integrity guards are intentionally hard to remove), but you can read, fork, and extend the source in the repo. You can also build your own private fork from it.
No. v4 is a rewrite on top of Effect — state management, error handling, and the runtime API all changed. Method names for most endpoints stayed close to the previous versions, but everything is wrapped in Effect now, and session/state handling works differently. Migration requires rework but not a full rewrite.
Node 22+.
No. The library relies on Node-specific crypto, networking, and native transport bindings.