Instagram Followers: Blue Checkmark Accounts & Bio Contacts

Instagram Scraper — Extract Followers, Verified Status & Bio Contacts

Instagram Followers: Blue Checkmark Accounts & Bio Contacts pulls follower counts, verified/business/professional status, and bio contacts (email, phone, link-in-bio) from public Instagram profiles, then drops every account that doesn't pass your qualifier filters. Feed it usernames, @handles, or profile URLs and get back typed, normalized JSON — no HTML, no selectors, no manual parsing. After reading this page you'll know which fields the Actor emits, how filters narrow the dataset to only qualifying accounts, and how to wire the output into a lead list or CRM.

What is Instagram Followers: Blue Checkmark Accounts & Bio Contacts?

Instagram Followers: Blue Checkmark Accounts & Bio Contacts is an Apify Actor that scrapes public Instagram profiles and qualifies each one against a filter suite — verified badge, business/professional flag, minimum media count, external link, bio email, and category — before it ever reaches the dataset. It also extracts bio contact details (email, phone number, bio links) straight from the profile's public bio text and link data. No Instagram account or login is required; the Actor reads the same public profile data a logged-out visitor sees.

• Qualify accounts by verified, business, or professional status
• Filter out accounts below a minimum post count, or without an external URL
• Extract bio contacts: email, phone number, and bio links
• Segment results by business/creator category with categoryFilters
• Export qualified accounts as JSON or CSV

What data does Instagram Followers: Blue Checkmark Accounts & Bio Contacts collect?

Every dataset row groups together account qualifiers, profile metrics, bio contacts, and a content-surface snapshot for one profile.

Data Type	Key Fields	JSON Field Names
Account qualifiers	verified badge, business flag, professional flag, private flag	isVerified, isBusinessAccount, isProfessionalAccount, isPrivate
Profile metrics & category	follower/following/post counts, category	followersCount, followsCount, postsCount, categoryName, businessCategory
Bio contacts	email, phone, website, bio links	bioEmail, bioPhone, externalUrl, bioLinks
Content-surface signals	highlight reels, IGTV videos, clips, channel	highlightReelCount, igtvVideoCount, hasClips, hasChannel
Recent posts snapshot	up to 12 latest posts with caption, likes, comments	latestPosts[].caption, latestPosts[].likesCount, latestPosts[].commentsCount

Need more Instagram data?

If you need follower counts tracked over time rather than a one-off snapshot, Instagram Followers Scraper: Daily Follower Counts is built for recurring growth tracking. If your workflow needs deeper business-lead enrichment beyond bio-text contacts, Instagram B2B Email Scraper With Business Profile Leads targets that specifically.

How does Instagram Followers: Blue Checkmark Accounts & Bio Contacts differ from the official Instagram API?

Instagram's Graph API (Meta's official API) requires a Business or Creator account linked to a Facebook Page and an approved developer app before it returns any profile data, and even then its Business Discovery feature only exposes fields for other public business accounts — not personal accounts, and no parsed bio email or phone number. Instagram Followers: Blue Checkmark Accounts & Bio Contacts reads any public profile from a plain username, handle, or URL, with no app review and no linked Business Page required.

Feature	Instagram Graph API	Instagram Followers: Blue Checkmark Accounts & Bio Contacts
Setup	Facebook Developer app + App Review approval	Provide input and start the run — no approval process
Account-type access	Business Discovery only reaches other Business accounts	Reads any public profile: personal, creator, or business
Login/account requirement	Requires a Business/Creator account linked to a Facebook Page	No Instagram login or linked account needed
Bio contact extraction	No endpoint parses bio email/phone from free text	Extracts bioEmail/bioPhone directly from bio text
Qualifier filtering	Client must build filtering logic on the raw response	Built-in filters (onlyVerified, onlyBusiness, minMediaCount, etc.) drop non-matching rows before output
Output format	Nested Graph API JSON requiring separate parsing	Flat, typed JSON with qualifiers already applied

The Graph API is the right choice when you already manage the accounts involved and need write-level Meta integration. This Actor is the more direct route when you need read-only qualification and bio contacts across public accounts you don't own or manage, without going through a developer-app review process.

Why do developers and teams scrape Instagram?

For B2B lead generation and sales teams

Sales and growth teams use categoryFilters combined with onlyBusiness to pull a list of business accounts in a specific niche — say, "Restaurant" or "Clothing" — and then requireBioEmail to keep only the accounts that already publish a contact email in their bio. The result is a ready-to-import outreach list: userName, categoryName, bioEmail, bioPhone, and externalUrl map directly onto CRM fields, without a human opening dozens of profiles one by one to copy contact details by hand into a spreadsheet before a single outreach email goes out.

For influencer marketing and brand partnership teams

Before signing a partnership, brand teams check isVerified, followersCount, postsCount, and categoryName together to vet whether an account is a legitimate, active, verified creator in the right niche rather than a bought-follower account. onlyVerified and minMediaCount filter out low-activity or unverified accounts in bulk, turning a shortlist of candidate handles gathered from a hashtag search or a competitor's tagged posts into a qualified vetting table in one run, instead of a marketer opening each profile manually and checking the badge one at a time.

For market researchers and analysts

Researchers studying a niche use categoryFilters and onlyProfessional to pull a public, category-segmented sample of professional accounts — for example, comparing verified-badge rates, average followersCount, or bio-email adoption across a set of "Clothing" versus "Restaurant" accounts — without touching any private or login-gated data. Because non-matching profiles are dropped before the dataset is written, the resulting sample is already segmented for analysis, so a spreadsheet of qualifying accounts is ready to summarize as soon as the run finishes, with no manual cleanup step first.

For developers building lead-enrichment pipelines

Developers building internal tools or CRM enrichment pipelines call the Actor by API, pass a batch of targetAccounts gathered from another source (a hashtag scrape, a CSV import, a form submission), and get back qualified, typed rows they can insert straight into a database or enrichment queue — bioEmail/bioPhone populate contact fields, and dataSource marks whether a row came from the full profile payload or the more limited meta-tag fallback, so a pipeline can flag lower-confidence rows for a manual double-check before they reach a live CRM record.

How to scrape Instagram (step by step)

1. Open Instagram Followers: Blue Checkmark Accounts & Bio Contacts on its Apify Store page (or call it through the Apify API).
2. Provide targetAccounts — a list of usernames, @handles, or profile URLs. The run fails immediately if this list is empty.
3. Set the qualifier filters you need (onlyVerified, onlyBusiness, onlyProfessional, excludePrivate, minMediaCount, requireExternalUrl, requireBioEmail, categoryFilters) — every account that doesn't pass is scraped, evaluated, then dropped from the output.
4. Start the run from the Console or via the API.
5. Open the Dataset tab to browse qualified accounts as they're pushed, then export as JSON or CSV.

What to do when Instagram changes its structure

The Actor already tries four extraction methods per profile — a direct API call plus three HTML-parsing fallbacks — before giving up, so isolated structure changes are absorbed automatically. It's maintained, and its output schema stays stable: field names and types don't change on your end. No specific turnaround time is guaranteed for fixes.

⬇️ Input

Parameter	Required	Type	Description	Example Value
targetAccounts	No	array	Instagram profile URLs, usernames, or @handles to scrape and qualify. Legacy key urls is also accepted.	["nike", "https://instagram.com/natgeo", "@nasa"]
onlyVerified	No	boolean	Keep only blue-badge verified accounts. Non-verified profiles are still fetched, then dropped. Default false.	true
onlyBusiness	No	boolean	Keep only accounts flagged as business accounts. Default false.	true
onlyProfessional	No	boolean	Keep only professional accounts (business or creator). Default false.	false
excludePrivate	No	boolean	Drop private profiles from the output. Default false.	true
minMediaCount	No	integer	Keep only accounts with at least this many posts. 0 = no minimum. Default 0.	50
requireExternalUrl	No	boolean	Keep only accounts with a website link in their bio. Default false.	true
requireBioEmail	No	boolean	Keep only accounts whose bio text contains an email address. Default false.	false
categoryFilters	No	array	Keep only accounts whose business/category name contains any of these terms (case-insensitive). Default [].	["Restaurant", "Clothing"]
proxyConfiguration	No	object	Proxy settings. Residential proxies are recommended for reliable results.	{"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"]}

None of the 10 parameters are marked required in the input schema, but the run raises an error immediately if targetAccounts (or the legacy urls key) is empty — the most common input mistake is leaving it out or passing an empty array.

Example input

{
  "targetAccounts": ["nike", "https://instagram.com/natgeo", "@nasa"],
  "onlyBusiness": true,
  "onlyVerified": true,
  "excludePrivate": true,
  "minMediaCount": 50,
  "requireExternalUrl": true,
  "requireBioEmail": false,
  "categoryFilters": ["Clothing", "Sports"],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}

⬆️ Output

Each qualified account is written as one typed, normalized JSON dataset row — no HTML, no nested Instagram GraphQL wrapper. Results export as JSON, CSV, Excel, or XML directly from the dataset. Only rows that pass every active qualifier filter are pushed, and each pushed row charges one row_result event — accounts that fail a filter, or fail to scrape, are never pushed and are never charged.

Scraped account profile

{
  "userId": "13460080",
  "userName": "nike",
  "userFullName": "Nike",
  "profilePic": "https://scontent.cdninstagram.com/v/nike_profile.jpg",
  "profilePicUrlHD": "https://scontent.cdninstagram.com/v/nike_profile_hd.jpg",
  "followersCount": 302000000,
  "followsCount": 128,
  "postsCount": 1200,
  "isVerified": true,
  "isBusinessAccount": true,
  "isProfessionalAccount": true,
  "isPrivate": false,
  "businessCategory": null,
  "businessCategoryName": null,
  "categoryName": "Sportswear store",
  "biography": "Just Do It",
  "externalUrl": "https://nike.com",
  "externalUrlShimmed": "https://l.instagram.com/?u=https%3A%2F%2Fnike.com",
  "bioLinks": [
    { "title": "Shop Nike", "url": "https://nike.com", "type": "external" }
  ],
  "bioEmail": null,
  "bioPhone": null,
  "highlightReelCount": 24,
  "igtvVideoCount": 3,
  "hasClips": true,
  "hasChannel": false,
  "isJoinedRecently": false,
  "pronouns": [],
  "latestPosts": [
    {
      "shortCode": "C1a2B3cDe4F",
      "url": "https://www.instagram.com/p/C1a2B3cDe4F/",
      "type": "Image",
      "caption": "New drop.",
      "likesCount": 452000,
      "commentsCount": 3100,
      "timestamp": "2026-07-01T15:04:00.000Z",
      "isVideo": false,
      "videoViewCount": null,
      "displayUrl": "https://scontent.cdninstagram.com/v/post_image.jpg"
    }
  ],
  "dataSource": "web_profile_info",
  "userUrl": "https://www.instagram.com/nike",
  "timestamp": "2026-07-25 - 14:02",
  "scrapedAt": "2026-07-25T14:02:11.483210+00:00"
}

How many results can you scrape with Instagram Followers: Blue Checkmark Accounts & Bio Contacts?

There's no hard cap coded into the Actor — the ceiling on any run is simply the number of accounts you list in targetAccounts. There's no pagination to configure, because each dataset row corresponds to one account you named as input, not to a paginated list Instagram serves back. Accounts are processed one at a time, with a fresh residential proxy IP and a randomized delay between each request, rather than in parallel batches. Accounts that fail a qualifier filter, or fail to scrape at all (private-without-data, deleted, or rate-limited), are logged and skipped rather than counted toward your output — the run continues to the next account instead of stopping. Because there's no benchmark run published for this Actor, no throughput or timing figure is claimed here; budget your run size around the number of accounts you actually need qualified.

Integrate Instagram Followers: Blue Checkmark Accounts & Bio Contacts and automate your workflow

Instagram Followers: Blue Checkmark Accounts & Bio Contacts works with any language or tool that can send an HTTP request.

REST API integration

import requests

TOKEN = "your-apify-token"
ACTOR = "instagram-followers-count-scraper-blue-checkmark-accounts-bio-contacts"
url = f"https://api.apify.com/v2/acts/{ACTOR}/run-sync-get-dataset-items"

payload = {
    "targetAccounts": ["nike", "natgeo"],
    "onlyBusiness": True,
    "requireBioEmail": True,
}

resp = requests.post(url, params={"token": TOKEN}, json=payload)
resp.raise_for_status()

for account in resp.json():
    print(account["userName"], account["bioEmail"])

Works in Python, Node.js, Go, Ruby, cURL.

MCP for AI agents

Apify's MCP server (mcp.apify.com) exposes Apify Actors — including this one — as callable tools for MCP-compatible clients such as Claude Desktop, Cursor, and Windsurf. Add the Actor's name (instagram-followers-count-scraper-blue-checkmark-accounts-bio-contacts) to the server's actor list to call it as an agent tool without writing custom integration code.

Automation platforms (n8n, Make, LangChain)

In n8n, the community Apify node's "Run Actor" operation can call this Actor by Actor ID, pass targetAccounts and your qualifier flags as JSON, and feed the resulting dataset items into downstream nodes such as a CRM upsert or a spreadsheet append. In Make, the Apify app's "Run an Actor or Task" module runs the same Actor and lets you map each qualified account's bioEmail, bioPhone, and categoryName into another scenario step, like a lead-routing workflow. Any LangChain agent that can call an HTTP tool can invoke the Actor through the Apify API and consume the returned dataset items as typed JSON without a parsing step.

Is it legal to scrape Instagram?

Scraping publicly accessible Instagram profile data is generally lawful, and Instagram Followers: Blue Checkmark Accounts & Bio Contacts only reads data a logged-out visitor can already see on a public profile — no login, and no private-account content. Because the output includes personal identifiers and contact details (bioEmail, bioPhone, userFullName), it falls under personal-data frameworks like GDPR and CCPA rather than pure business/database-rights rules — you're responsible for having a lawful basis before storing or using bio contacts for outreach. Consult legal counsel for commercial use cases involving bulk personal data.

Frequently asked questions

Does Instagram Followers: Blue Checkmark Accounts & Bio Contacts work without an Instagram account?

Yes. No Instagram login or account is required — the Actor reads the same public profile data a logged-out visitor sees.

How often is the scraped data updated?

Every run performs a live fetch against Instagram for each account in targetAccounts. Nothing is served from a cache; each run reflects the profile's current public state at run time.

What happens if a target account doesn't exist or was deleted?

That account fails to scrape and is logged as a failed scrape rather than included in the output — the run continues processing the rest of your list instead of stopping, and the failed account simply isn't in your dataset.

Can I scrape private Instagram accounts?

No. Only publicly accessible profile data is returned. Private accounts are still included in the output by default (with isPrivate: true), but you can set excludePrivate to true to drop them from the dataset entirely.

Do the qualifier filters affect how much I'm charged?

Yes, in your favor. Only accounts that pass every active filter are pushed to the dataset, and each pushed row charges one row_result event — accounts filtered out or failed to scrape are never pushed, so you aren't charged for them.

Does Instagram Followers: Blue Checkmark Accounts & Bio Contacts work for AI agent workflows and LLM pipelines?

Yes. It's callable as an HTTP endpoint through the Apify API from any agent framework, and it's reachable through Apify's MCP server as a callable tool — every response is typed JSON with stable field names, so no parsing step is needed before passing results to an LLM.

How does Instagram Followers: Blue Checkmark Accounts & Bio Contacts handle Instagram's anti-bot system?

It fetches Instagram's web_profile_info endpoint and profile pages using a Chrome TLS/HTTP2 impersonation client so requests aren't fingerprinted as a plain Python client, rotates a fresh residential proxy IP per profile when proxies are enabled, and retries failed requests with backoff before falling back to HTML parsing.

Does Instagram Followers: Blue Checkmark Accounts & Bio Contacts return data in a format LLMs can use directly?

Yes. Output is typed, normalized JSON with stable field names, so it can be passed directly into an LLM context window, indexed into a vector store, or routed through an agent tool without extra parsing.

Can I use Instagram Followers: Blue Checkmark Accounts & Bio Contacts without managing proxies?

Yes. If you omit proxyConfiguration, the Actor connects directly with no proxy. The Console's default input prefills a residential proxy group, since Instagram's anti-bot system responds more reliably to residential IPs, but you can remove it for a direct connection.

What happens when Instagram changes its structure or blocks the scraper?

The Actor is maintained, and its output schema stays stable — field names and types don't change on your end. It already falls back through multiple extraction methods per profile before failing, which absorbs many structure changes automatically. No specific turnaround time is guaranteed for fixes.

Your feedback

Found a bug, or a field that's missing from your results? We want to know. Report it through the Issues tab on this Actor's Apify Store page, or reach out to API-Empire through Apify Console — active reports directly shape what gets fixed and maintained next.