Instagram Profile Scraper
Any public Instagram profile as typed JSON: bio, follower, following and post counts, verified and private flags, highlight count and profile picture. 1 credit per profile. No Instagram login, no proxies.
Free API key · 1 credit per profile · failed calls free
// GET /api/v2/instagram-profile/?usernames=mrbeast · sample from the catalog { "success": true, "data": { "usernames": "mrbeast", "profile": { "inputUrl": "https://www.instagram.com/mrbeast/", "url": "https://www.instagram.com/mrbeast", "id": "2278169415", "username": "mrbeast", "fullName": "MrBeast", "biography": "Video Philanthropist 💰", "followersCount": 456000000, "followsCount": 500, "postsCount": 350, "verified": true, "private": false, "highlightReelCount": 5, "profilePicUrl": "https://instagram.fbhk1-3.fna.fbcdn.net/v/t51.2885-19/mrbeast_profile.jpg" }, "next_cursor": null } }
| field | value | type | Has a value✓ |
|---|
Scrapier's Instagram Profile Scraper returns a public Instagram profile as JSON: username, fullName, biography, followersCount, followsCount and postsCount, verified and private flags, highlight count and profile picture URL. It costs 1 credit per successful call. No Instagram login.
Instagram Profile Scraper extracts any public Instagram profile: username, full name, biography, follower, following and post counts, verified and private flags, highlight count and profile picture. Every response is structured JSON, ready to pass directly to an LLM, index into a vector store or feed a monitoring pipeline. It is one of 20 Instagram endpoints on the same API key used by 12,000+ developers. Point it at one handle today and a list of thousands tomorrow: the call stays the same.
What data can I extract with Instagram Profile Scraper?
Using this Instagram Profile Scraper, you can extract the following data from public Instagram profiles:
Want the exact field names? See the example output.
Try Instagram Profile Scraper Live
Press Run to see the catalog sample. Add your API key and it runs a real call to the Scrapier API from your browser. The key is sent only to proxy.scrapier.io and never stored.
+ Run live with your API key
How to use Instagram Profile Scraper
Hand it to your AI assistant, or run it yourself in five steps.
Copy to your AI assistant
Paste this into ChatGPT, Claude or Cursor and it knows how to call the scraper.
Use the Scrapier Instagram Profile Scraper to get public Instagram profiles. Endpoint: GET https://proxy.scrapier.io/api/v2/instagram-profile/?usernames={usernames} with header "X-API-Key: YOUR_API_KEY" and a 210-second timeout. Send one value per call in usernames; for a list, make one call per value, at most 3 in parallel. It returns JSON under data.profile: inputUrl, url, id, username, fullName, biography, followersCount, followsCount, postsCount, verified, private, highlightReelCount. Each successful call costs 1 credit; failed calls are free. If you support MCP, run: claude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY" and call run_scrape with endpoint "instagram-profile" (find it with search_endpoints).Use this scraper from ChatGPT, Claude or Cursor. Point your assistant at Scrapier and it reads Instagram profiles on its own: no glue code, no scraping logic in your prompts.
Run it yourself
- Get your free Scrapier API keySign up at app.scrapier.io; the free tier lets you try it first.
- Open Instagram Profile Scraper in the catalogIt lives under Scrapers / Instagram.
- Enter the Instagram username or profile URLFor example
mrbeast,@mrbeastorhttps://www.instagram.com/mrbeast/. - Send your API requestOne GET with your key in the
X-API-Keyheader, or onerun_scrapecall from your agent. - Save your resultsThe profile comes back as JSON in
data.profile: store it as is, or flatten it to CSV in a few lines.
How to scale to bulk Instagram profiles
usernames takes one username per call, so for a list you loop: one request per handle. Run up to 3 requests in parallel per API key; above that the API answers 429 with a Retry-After header, and throttled calls cost nothing. Each profile is 1 credit and failed calls are free, so 1,000 profiles cost 1,000 credits, inside the Hobby plan's 15,000. Read handles from a file, call three at a time, and retry a 429 after the delay it gives.
Features
Instagram Profile Scraper fetches clean, structured profile data from public Instagram accounts at low cost. It suits influencer research, competitor tracking, lead enrichment and any workflow that needs reliable profile metadata.
- Identityusername, full name, ID, profile URL and profile picture
- Audiencefollower, following and post counts as integers
- Statusverified badge and private flag
- Highlightsnumber of story highlights on the profile
- Freshness
scraped_at, the time Scrapier read the profile
Proxies, retries and parsing run on Scrapier's side, so you send one request and get JSON back, at 1 credit per profile and 0 credits for a failed call.
Use cases
- Influencer marketer pulls follower count, verified badge and bio for 500 handles, then keeps only public accounts between 10k and 250k followers before outreach.
- Brand analyst calls the scraper daily for five competitor accounts and charts follower and post-count growth week over week.
- Sales team enriches a lead list with each brand's Instagram follower count and verified status, so reps call the accounts with real audiences first.
- Agency strategist compares a client's follower, following and post counts with five peers each month to show where the account stands.
- AI engineer feeds profile bios and counts into a RAG index, so a support agent can answer "who is this creator?" with live data and its
scraped_attime.
Running these from an agent? Use the MCP integration and let Claude or Cursor call the scraper directly.
Why choose this Scraper API?
Each call reads the profile at call time, and the response carries scraped_at, so you know exactly how fresh every number is.
Instagram's app shows "456M". The scraper returns followersCount as an integer (456000000 in the catalog sample), plus following and post totals, ready to sort and chart.
Profiles, posts, reels, comments, hashtags and highlights share the same key and response envelope, so moving from profile to posts is a change of endpoint, not of code.
Input
The scraper takes one Instagram username, @handle or profile URL per call in usernames. Everything else is optional. Send parameters in the query string (GET) or as a JSON body (POST).
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
usernames | string | Yes | — | Instagram username, @handle or profile URL. One per call. Aliases: username, url, urls |
include_about | boolean | No | false | Adds an about block (joined date, country). Usually null |
cursor | string | No | — | Pass back data.next_cursor for the next page; null for a single profile |
use_proxy | boolean | No | true | Route through Scrapier's residential proxy pool. Leave as is |
raw_data | boolean | No | false | Return Instagram's raw upstream payload under raw_responses instead of the formatted profile |
One username per call: to look up ten profiles, make ten calls. Booleans are the strings true or false.
Example input
{
"usernames": "mrbeast",
"include_about": "false",
"use_proxy": "true",
"raw_data": "false"
}Error codes
| Status | Meaning | Billed | Fix |
|---|---|---|---|
| 200 | Profile data returned in data.profile | Yes | — |
| 400 | Bad or missing input | No | Check usernames: one value per call |
| 401 | X-API-Key header missing | No | Add the header |
| 402 | Out of credits (body has balance) | No | Top up; retrying will not help |
| 403 | Invalid or revoked API key | No | Check the key in your dashboard |
| 429 | Throttled | No | Wait Retry-After seconds, then retry |
| 5xx | Upstream failure or timeout | No | Retry with backoff; set a 210 s client timeout |
From the error reference. Any non-2xx response costs 0 credits.
Output
Typed JSON with the same schema on every call. One call returns one profile object with 17 fields for one public account, inside the standard data envelope. Field names stay the same on every call, so code and agents read them directly.
Example output
{
"success": true,
"data": {
"usernames": "mrbeast",
"profile": {
"inputUrl": "https://www.instagram.com/mrbeast/",
"url": "https://www.instagram.com/mrbeast",
"id": "2278169415",
"username": "mrbeast",
"fullName": "MrBeast",
"biography": "Video Philanthropist 💰",
"followersCount": 456000000,
"followsCount": 500,
"postsCount": 350,
"verified": true,
"private": false,
"highlightReelCount": 5,
"profilePicUrl": "https://instagram.fbhk1-3.fna.fbcdn.net/v/t51.2885-19/mrbeast_profile.jpg",
"relatedProfiles": [],
"latestIgtvVideos": [],
"latestPosts": [],
"scraped_at": "2026-03-09T15:19:49.021Z"
},
"next_cursor": null
}
}The catalog's sample response for usernames=mrbeast, labelled as a sample: live calls return the account's current values.
Identity fields
| Field | Type | Example | Description |
|---|---|---|---|
profile.id | string | "2278169415" | Instagram's numeric account ID, as a string |
profile.username | string | "mrbeast" | Handle without the @ |
profile.fullName | string | "MrBeast" | Display name on the profile |
profile.biography | string | "Video Philanthropist 💰" | Bio text as shown on the profile |
profile.profilePicUrl | string | "https://instagram.fbhk1-3.fna.fbcdn.net/v/t…" | Profile picture URL on Instagram's CDN |
profile.url | string | "https://www.instagram.com/mrbeast" | Canonical profile URL |
profile.inputUrl | string | "https://www.instagram.com/mrbeast/" | Profile URL built from your input |
Status and audience counts
| Field | Type | Example | Description |
|---|---|---|---|
profile.verified | boolean | true | Verified badge |
profile.private | boolean | false | true when the account is private |
profile.followersCount | integer | 456000000 | Followers, as Instagram reports them |
profile.followsCount | integer | 500 | Accounts this profile follows |
profile.postsCount | integer | 350 | Posts on the profile |
profile.highlightReelCount | integer | 5 | Story highlights on the profile |
Content and related arrays
| Field | Type | Example | Description |
|---|---|---|---|
profile.latestPosts | array | [] | Recent posts; empty in the sample. Use Profile Posts or Profile Full for posts |
profile.latestIgtvVideos | array | [] | Recent IGTV videos; empty in the sample |
profile.relatedProfiles | array | [] | Related accounts; empty in the sample. Related Profiles returns them |
Response envelope
| Field | Type | Example | Description |
|---|---|---|---|
success | boolean | true | true on every 200 response |
data.usernames | string | "mrbeast" | Your input, echoed back |
data.next_cursor | null | null | null here: a profile is a single lookup |
profile.scraped_at | string | "2026-03-09T15:19:49.021Z" | When Scrapier fetched the profile (ISO 8601, UTC) |
How does it work?
Scrapier sends each request through its residential proxy pool (use_proxy, on by default), so you never manage IPs or proxy accounts.
Retries and parsing of Instagram's pages happen on Scrapier's side. You send one HTTP request and get typed JSON back.
Only publicly visible data is returned: what any visitor sees without logging in. No Instagram account or cookie is used for this endpoint.
The schema is stable. When Instagram changes its pages, Scrapier updates the scraper; the field names in data.profile stay the same.
How do you integrate Instagram Profile Scraper into your stack?
It works with what you already use: any HTTP client, AI agents over MCP, and no-code automation tools. Code samples for cURL, Python and Node.js are on the API tab.
MCP integration for AI agents
This registers the Scrapier MCP server, whose tools reach every Scrapier scraper, including instagram-profile: the agent finds it with search_endpoints and calls it with run_scrape. Works with Claude Code, Cursor and Windsurf. MCP calls are billed like REST: 1 credit per successful call. Full MCP setup →
No-code tools (n8n, Make, LangChain)
Use the HTTP Request node with your Scrapier API key in an X-API-Key header and point it at /api/v2/instagram-profile/ with a usernames query parameter. Map data.profile into the next node.
Add an HTTP "Make a request" module with the same header and URL, and parse the response as JSON. Map followersCount or verified straight into Sheets or your CRM.
Wrap the endpoint in a requests-based tool, or load the Scrapier MCP server through LangChain's MCP adapters so the agent finds instagram-profile with search_endpoints itself.
Pricing and Rate Limits
One Instagram profile costs 1 credit, so 1,000 profiles cost 1,000 credits: $1.58 on the Pro plan. Failed and empty calls are not billed. Run up to 3 requests in parallel per key; above that the API answers 429 with a Retry-After header.
| Plan | Monthly price | Credits | Profiles included | Per 1,000 profiles |
|---|---|---|---|---|
| Hobby | $29 | 15,000 | 15,000 | $1.93 |
| Pro | $79 | 50,000 | 50,000 | $1.58 |
| Scale | $299 | 250,000 | 250,000 | $1.20 |
| Enterprise | Custom volume and terms | |||
Prices from the live billing page. See all plans and limits.
Call cost and timing
How we measure this
Credit cost, pagination and the sample come from the live catalog (GET /api/v2/endpoints, /instagram-profile/, checked 9 Nov 2026). Concurrency and timeout guidance come from the rate limits page of the docs. Scrapier does not publish latency or success-rate figures for this endpoint, so none are shown here.
Instagram Profile Scraper vs the Official Instagram API
| Feature | Scrapier profile scraper | Instagram Graph API |
|---|---|---|
| Access needed | One Scrapier API key | Meta app, Instagram professional account and access token |
| Which profiles | Any public account | Other business and creator accounts via Business Discovery |
| Fields returned | 17 profile fields, including bio and highlight count | Business Discovery fields such as followers_count, media_count and biography |
| Rate limits | Up to 3 parallel requests per key; 429 with Retry-After | Meta's Graph API rate limits per app and user |
| App review | None | Required for advanced access |
| Cost | 1 credit per profile, from $1.20 per 1,000 profiles | Free once approved |
The official API is the better choice for reading your own account's insights. The Instagram Basic Display API was shut down on 4 December 2024.
Is it legal to scrape Instagram data?
Scraping publicly available Instagram profile data is generally lawful in many countries, but the answer depends on what you collect, where you are and how you use it. In the US, hiQ Labs v. LinkedIn is the case most often cited on public-data scraping. Scrapier returns only data any visitor can see without logging in. Under GDPR and similar laws, collecting public data can be permissible, but how you store and use personal data must still comply with local data-protection rules, and Instagram's terms apply. Consult legal counsel if your use case involves bulk storage of personal data. This is not legal advice; see our Terms of Use.
Frequently asked questions
What fields does Instagram Profile Scraper return?
The top five are username, fullName, followersCount, postsCount and verified, plus biography, followsCount, private, highlightReelCount, profilePicUrl, the profile URL and scraped_at: 17 fields in data.profile. Each successful call costs 1 credit and needs no Instagram login.
Does Instagram Profile Scraper require an Instagram account or login?
No. The Instagram Profile Scraper uses no Instagram account or cookies: you send your Scrapier API key in the X-API-Key header and a username, and get JSON back. Only public profile data is returned.
How fast does Instagram Profile Scraper run?
Scrapier does not publish a latency figure for this endpoint. Each call is a single lookup that reads the profile live, and scraped_at in the response records when. Set a client timeout of 210 seconds, as the docs recommend for every endpoint.
What happens if a profile is private or doesn't exist?
A private account returns private: true with only what Instagram shows logged-out visitors, and no posts. If the call fails, for example because the username does not exist, the API returns a non-2xx status and the call costs 0 credits. In code, check the status and skip or re-check the handle.
Can I scrape multiple Instagram profiles at once?
Yes, with one call per username: usernames takes a single value. Loop over your list and run up to 3 requests in parallel per API key. 1,000 profiles cost 1,000 credits; failed and throttled calls are free.
Does Instagram Profile Scraper work with Claude, ChatGPT and other AI agent tools?
Yes. Connect the Scrapier MCP server with claude mcp add -t http scrapier https://mcp.scrapier.io/mcp and your API key in an X-API-Key header; it works in Claude Code, Cursor and Windsurf. The agent finds instagram-profile with search_endpoints and calls it with run_scrape. Any agent that can call an HTTP endpoint can use the REST API directly.
How does it compare to other Instagram profile scrapers?
Scrapier charges a flat 1 credit per successful profile call, and failed calls are free; platforms that bill compute units vary with run time and infrastructure. The same API key and MCP server reach all 199 Scrapier endpoints. Scrapier returns structured JSON for public profiles.
Does it return data in a format LLMs can use directly?
Yes. Every response is typed JSON with the same field names on every call: no HTML parsing and no selectors. Pass it straight to an LLM, index it into a vector store or return it from an agent tool.
What happens when Instagram changes its layout or anti-bot system?
Scrapier maintains the scraper. When Instagram changes its pages, Scrapier updates it, and your calls keep returning the same JSON field names without changes on your end.
Can I use it without managing proxies or browsers?
Yes. Proxy routing, retries and parsing are handled by Scrapier. You send one HTTP request with your API key and get structured JSON back: no proxy accounts and no headless browser to run.
Which profile fields work best for AI training data and RAG?
For RAG, biography, fullName, username and url give rich entity context. For training data, followersCount, followsCount, postsCount and verified are the most consistent. All are typed strings, integers and booleans.
How much does it cost to scrape 1,000 Instagram profiles?
1,000 credits, because each profile is one call at 1 credit. That is about $1.93 on Hobby, $1.58 on Pro and $1.20 on Scale, at the plans' price per credit. Failed calls are free.
How do I scrape Instagram profiles with Python?
Send a GET request with the requests library to https://proxy.scrapier.io/api/v2/instagram-profile/ with params={"usernames": "mrbeast"}, your key in the X-API-Key header and timeout=210. Read r.json()["data"]["profile"]: it is already JSON, so no HTML parsing is needed.
Is it legal to scrape Instagram profiles?
It depends on your use and your country, so this is not legal advice. Scrapier returns public profile data only. Instagram's terms and privacy law such as GDPR or CCPA apply to how you store and use it. Collect only what you need, and ask a lawyer about your specific case.
Your feedback
Found a bug or missing a field? Let us know. Write to support@scrapier.io and the team replies to every report.
Start Scraping Instagram Profiles
Public Instagram profiles as JSON, 1 credit each, from REST or MCP.