A REST API for public Instagram data: send a username or a post link with your API key and get profiles, posts, reels, stories and highlights back as JSON. We keep the Instagram sessions, logins and limits working for you.
Illustrative response. Run real lookups in the Instagram viewer.
Six data endpoints cover what people actually need from a public account, plus an image proxy and a download endpoint for the media, all as structured JSON. Looking for an Instagram scraper API? With this API you don’t run scrapers, headless browsers, proxies or Instagram logins yourself: you send an HTTP request and read JSON.
Followers, following, posts, bio, verification, business and contact fields.
Paginated posts with media, captions and engagement counts via cursor paging.
Resolve any post or reel by URL or shortcode into full media details.
Currently active stories for an account, when they are public.
The highlight trays on a profile, and the items inside each one.
Show Instagram CDN images from your own origin, and save any photo or video as a file.
The Instagram viewer calls the same endpoints from your browser, no key needed: open a profile, page through a feed, paste a post link or save stories and highlights.
One page for each kind of content, each with the same box: paste an Instagram link or type a username, then download. No key and no sign-in.
The hard part of Instagram data isn't the JSON — it's staying logged in. IGAPI runs a pool of real accounts so you never touch any of it.
Requests spread across many logged-in accounts and rotate automatically under load.
2FA, security challenges and expired sessions are resolved and re-logged in without you.
A key's plan can cap it per minute, day and month (UTC). A capped request gets a 429 naming the plan and the full window, with Retry-After, so clients know when to retry.
Every error from the data endpoints has a code, an HTTP status and a message; the documentation lists each one with an example.
Get an API key on the pricing page, send it in the X-API-Key header, read JSON back.
Every plan calls the same endpoints; plans differ only in how many requests a key may make, counted per key in UTC minutes, days and months. At a cap the API answers 429 with Retry-After — nothing is billed.
For apps and side projects
Hard caps, no overage
For high-volume services
Hard caps, no overage
For growing products
Hard caps, no overage
Caps are hard limits: past a cap the API answers 429 with Retry-After until that window resets. No overage charges. How buying works: the button opens a Telegram chat with @im_rashid with the plan already named. Payment is arranged there for now; crypto checkout is planned. A key that moves to another plan stays the same key.
Need more than Mega? Contact us on Telegram with the volume you expect.
Contact usThe full details — what counts as a request, the API at a glance and answers to common questions — are on the Instagram API pricing page.
Read the full reference and run live calls in the playground, or try a lookup right now.