$1.59/1000
results
Bulk Instagram profile enrichment — username, bio, counts, public email, external links, and verification status without login cookies. Free plan: 100 profiles total; paid plans unlock unlimited volume.
Bulk Instagram profile enrichment — username, bio, counts, public email, external links, and verification status without login cookies. Free plan: 100 profiles total; paid plans unlock unlimited volume.
Validate creators, enrich leads, or seed downstream scrapers — baseline profile metadata in structured JSON.
On Scrapy.io, Instagram Profile Bulk Extractor by Thunderbolt is built for apify instagram scraper workflows — run from the Store, schedule recurring jobs, or POST to thunderbolt.p.scrapy.io from your stack.
usernamesInstagram drives creator marketing and brand monitoring — profile stats and public signals that rarely fit in official APIs. A apify instagram scraper workflow on Scrapy.io turns handles into warehouse rows your analytics stack can join to CRM and ads data.
Instagram Profile Bulk Extractor supports batch inputs with explicit caps so large audiences stay within budget. Export from the Store or POST the same payload to Thunderbolt’s publisher API.
This apify instagram scraper on Scrapy.io exports structured fields including:
For your first run, keep caps low (maxResults, maxReviews, etc.) until you validate row shape in the Output preview.
Teams discover Instagram Profile Bulk Extractor while researching apify instagram scraper and related terms such as instagram scraper, ig followers tool, download instagram followers, scrape instagram. This listing is structured to answer common questions — including — with concrete Input and Output examples you can run on Scrapy.io without maintaining your own scraper infrastructure.
If you arrived from SEO or paid search, start with the Input JSON example below, run once on the free tier, then scale with schedules or the publisher API once row shape and cost look right.
Use this checklist before your first production run of Instagram Profile Bulk Extractor:
maxResults, maxReviews, or equivalent limits so a full batch stays within budgetthunderbolt.p.scrapy.io/instagram-profile-scraper/v1/api or create a scheduled jobMost teams keep a "golden" input file in git for Instagram Profile Bulk Extractor so staging and production use identical payloads. Update that file when you add keywords, targets, or communities — not the orchestration code around it.
List public Instagram usernames (without @) in usernames. No login cookies or session IDs required.
Configure the run in the Scrapy.io input form or pass JSON to the publisher API.
{
"usernames": [
"instagram"
]
}| Field | Type | Required | Description |
|---|---|---|---|
usernames | string[] | Yes | List of Instagram usernames/userId/URL to scrape. Enter one username/userId/URL per line. Also accepted: username (Single-handle alias); or input (Single-handle alias). |
Results appear in the Scrapy.io run Output tab. Profiles and Errors tables in the run output.
Each successful row is designed for warehouse loads: stable column names, explicit error rows, and caps you control in the input form.
{
"username": "nike",
"full_name": "Nike",
"biography": "Just Do It.",
"followers": 300000000,
"following": 150,
"is_verified": true,
"external_url": "https://www.nike.com"
}Download the full dataset as JSON, CSV, or Excel from the Output tab, or fetch results programmatically via the publisher API after the run completes.
validate handles before partnership outreach
Teams usually snapshot these rows on a schedule, store a scrapedAt timestamp in their warehouse, and diff week-over-week to spot new entries or metric changes. For first-time setup, run Thunderbolt with conservative caps, validate the Output preview against your schema, then promote the same JSON to a cron or API job. Document which Output view (Posts, Comments, Reviews, etc.) your downstream models consume so new teammates can reproduce the pipeline without tribal knowledge.
attach Instagram stats to CRM contacts
Teams usually snapshot these rows on a schedule, store a scrapedAt timestamp in their warehouse, and diff week-over-week to spot new entries or metric changes. For first-time setup, run Thunderbolt with conservative caps, validate the Output preview against your schema, then promote the same JSON to a cron or API job. Document which Output view (Posts, Comments, Reviews, etc.) your downstream models consume so new teammates can reproduce the pipeline without tribal knowledge.
snapshot profile metrics for reporting
Teams usually snapshot these rows on a schedule, store a scrapedAt timestamp in their warehouse, and diff week-over-week to spot new entries or metric changes. For first-time setup, run Thunderbolt with conservative caps, validate the Output preview against your schema, then promote the same JSON to a cron or API job. Document which Output view (Posts, Comments, Reviews, etc.) your downstream models consume so new teammates can reproduce the pipeline without tribal knowledge.
branch into other social scrapers after lookup
Teams usually snapshot these rows on a schedule, store a scrapedAt timestamp in their warehouse, and diff week-over-week to spot new entries or metric changes. For first-time setup, run Thunderbolt with conservative caps, validate the Output preview against your schema, then promote the same JSON to a cron or API job. Document which Output view (Posts, Comments, Reviews, etc.) your downstream models consume so new teammates can reproduce the pipeline without tribal knowledge.
Designed for ~500 profiles per minute API flows on paid tiers — no session cookies required. Prefer Thunderbolt when profile batches must complete in enrichment queues, not manual exports.
Instagram Profile Bulk Extractor is rarely the only step in a data workflow. Teams typically:
usernamescrapedAt — refresh on a 30–90 day cadenceSee Related Thunderbolt tools below for same-publisher companions you can chain without leaving the Scrapy.io billing account.
Most production deployments follow the same shape:
postUrl, placeId, videoId, reviewId, …) plus scrape date where history mattersInstagram Profile Bulk Extractor separates successful rows from per-input errors, so staging logic can WHERE type != 'error' (or the equivalent filter for your tool) without failing the whole batch. Join across Thunderbolt tools on those stable keys to build multi-step datasets without re-scraping upstream steps.
Maintaining Facebook, LinkedIn, Instagram, or X extractors in-house means handling rate limits, HTML or API changes, proxy rotation, and observability — work that rarely differentiates your product. Instagram Profile Bulk Extractor on Scrapy.io outsources that operational burden: you supply inputs, Scrapy.io runs the job, and you pay per successful row.
Thunderbolt listings add API-first, warehouse-ready documentation (clear caps, field lists, and pipeline patterns) so data teams can onboard without reading executor source code. When requirements change, update the input JSON or schedule — not your scraper fleet.
Instagram Profile Bulk Extractor runs on Scrapy.io support multiple ways to get data out:
For production pipelines, most teams land JSON in object storage, normalize in dbt or Spark, and schedule recurring runs so the Store listing becomes just another data source — not a manual step.
Run Instagram Profile Bulk Extractor once from the Store to validate inputs, then promote the same JSON payload to a scheduled job on Scrapy.io. Common patterns:
thunderbolt.p.scrapy.io on a queueThunderbolt tools use pay-per-result billing, so scheduled jobs stay predictable when you cap maxResults, max_posts, max_comments, or equivalent limits in the input form.
curl -X POST "https://thunderbolt.p.scrapy.io/instagram-profile-scraper/v1/api" \
-H "Content-Type: application/json" \
-H "X-API-Key: YOUR_API_KEY" \
-d '{
"usernames": ["nike", "natgeo"]
}'Bulk runs via the scraper endpoint:
curl -X POST "https://thunderbolt.p.scrapy.io/instagram-profile-scraper/v1/scraper" \
-H "Content-Type: application/json" \
-H "X-API-Key: YOUR_API_KEY" \
-d '{
"usernames": ["nike", "natgeo"]
}'Open the API tab on the Store listing for Python, JavaScript, cURL, OpenAPI, and MCP snippets.
Instagram Profile Bulk Extractor is available through the Scrapy.io MCP server — configure your API key in Cursor, Claude Desktop, or another MCP client, then invoke the tool from agent workflows. This is useful for ad-hoc research ("scrape these ten URLs and summarize the Output") without writing boilerplate HTTP code.
For production, prefer the publisher API or scheduled runs; use MCP for exploratory analysis and internal tooling where a human or agent supplies inputs interactively. See the API tab on Instagram Profile Bulk Extractor for MCP connection snippets.
| Tool | Best for |
|---|---|
| LinkedIn Profile Lead Scraper | Thunderbolt companion tool — overview |
| X Profile Insights Extractor | Thunderbolt companion tool — overview |
| X Profile Posts & Replies Collector | Thunderbolt companion tool — overview |
Batch usernames in API jobs for enrichment queues
Index warehouse tables on username for deduplication
Start with small batches to validate field shape in Output preview
Inspect per-row errors in the Errors output view instead of failing an entire batch
Facebook-heavy runs failing in a pattern? Use Issues on this Thunderbolt listing and attach your run ID plus one post, page, or search query
Instagram Profile Bulk Extractor collects publicly available data only. You are responsible for complying with platform terms, applicable laws, and data-protection regulations (including GDPR when personal data is involved). Consult your legal team for your specific use case.
Yes. Use webhooks, scheduled runs, or the publisher API to push data into your warehouse, CRM, or automation stack.
Yes. POST to https://thunderbolt.p.scrapy.io/instagram-profile-scraper/v1/api with your API key. See the API tab on the Store listing for ready-made snippets.
Yes. Configure the Scrapy.io MCP endpoint with your API key to query Instagram Profile Bulk Extractor from AI assistants and agent workflows.
Thunderbolt focuses on Meta and social discovery workflows — leave a Reviews note if this actor saved you from browser scraping and which Facebook surface you use daily.
Validate creators, enrich leads, or seed downstream scrapers — baseline profile metadata in structured JSON.
On Scrapy.io, Instagram Profile Bulk Extractor by Thunderbolt is built for apify instagram scraper workflows — run from the Store, schedule recurring jobs, or POST to thunderbolt.p.scrapy.io from your stack.
usernamesInstagram drives creator marketing and brand monitoring — profile stats and public signals that rarely fit in official APIs. A apify instagram scraper workflow on Scrapy.io turns handles into warehouse rows your analytics stack can join to CRM and ads data.
Instagram Profile Bulk Extractor supports batch inputs with explicit caps so large audiences stay within budget. Export from the Store or POST the same payload to Thunderbolt’s publisher API.
This apify instagram scraper on Scrapy.io exports structured fields including:
For your first run, keep caps low (maxResults, maxReviews, etc.) until you validate row shape in the Output preview.
Teams discover Instagram Profile Bulk Extractor while researching apify instagram scraper and related terms such as instagram scraper, ig followers tool, download instagram followers, scrape instagram. This listing is structured to answer common questions — including — with concrete Input and Output examples you can run on Scrapy.io without maintaining your own scraper infrastructure.
If you arrived from SEO or paid search, start with the Input JSON example below, run once on the free tier, then scale with schedules or the publisher API once row shape and cost look right.
Use this checklist before your first production run of Instagram Profile Bulk Extractor:
maxResults, maxReviews, or equivalent limits so a full batch stays within budgetthunderbolt.p.scrapy.io/instagram-profile-scraper/v1/api or create a scheduled jobMost teams keep a "golden" input file in git for Instagram Profile Bulk Extractor so staging and production use identical payloads. Update that file when you add keywords, targets, or communities — not the orchestration code around it.
List public Instagram usernames (without @) in usernames. No login cookies or session IDs required.
Configure the run in the Scrapy.io input form or pass JSON to the publisher API.
{
"usernames": [
"instagram"
]
}| Field | Type | Required | Description |
|---|---|---|---|
usernames | string[] | Yes | List of Instagram usernames/userId/URL to scrape. Enter one username/userId/URL per line. Also accepted: username (Single-handle alias); or input (Single-handle alias). |
Results appear in the Scrapy.io run Output tab. Profiles and Errors tables in the run output.
Each successful row is designed for warehouse loads: stable column names, explicit error rows, and caps you control in the input form.
{
"username": "nike",
"full_name": "Nike",
"biography": "Just Do It.",
"followers": 300000000,
"following": 150,
"is_verified": true,
"external_url": "https://www.nike.com"
}Download the full dataset as JSON, CSV, or Excel from the Output tab, or fetch results programmatically via the publisher API after the run completes.
validate handles before partnership outreach
Teams usually snapshot these rows on a schedule, store a scrapedAt timestamp in their warehouse, and diff week-over-week to spot new entries or metric changes. For first-time setup, run Thunderbolt with conservative caps, validate the Output preview against your schema, then promote the same JSON to a cron or API job. Document which Output view (Posts, Comments, Reviews, etc.) your downstream models consume so new teammates can reproduce the pipeline without tribal knowledge.
attach Instagram stats to CRM contacts
Teams usually snapshot these rows on a schedule, store a scrapedAt timestamp in their warehouse, and diff week-over-week to spot new entries or metric changes. For first-time setup, run Thunderbolt with conservative caps, validate the Output preview against your schema, then promote the same JSON to a cron or API job. Document which Output view (Posts, Comments, Reviews, etc.) your downstream models consume so new teammates can reproduce the pipeline without tribal knowledge.
snapshot profile metrics for reporting
Teams usually snapshot these rows on a schedule, store a scrapedAt timestamp in their warehouse, and diff week-over-week to spot new entries or metric changes. For first-time setup, run Thunderbolt with conservative caps, validate the Output preview against your schema, then promote the same JSON to a cron or API job. Document which Output view (Posts, Comments, Reviews, etc.) your downstream models consume so new teammates can reproduce the pipeline without tribal knowledge.
branch into other social scrapers after lookup
Teams usually snapshot these rows on a schedule, store a scrapedAt timestamp in their warehouse, and diff week-over-week to spot new entries or metric changes. For first-time setup, run Thunderbolt with conservative caps, validate the Output preview against your schema, then promote the same JSON to a cron or API job. Document which Output view (Posts, Comments, Reviews, etc.) your downstream models consume so new teammates can reproduce the pipeline without tribal knowledge.
Designed for ~500 profiles per minute API flows on paid tiers — no session cookies required. Prefer Thunderbolt when profile batches must complete in enrichment queues, not manual exports.
Instagram Profile Bulk Extractor is rarely the only step in a data workflow. Teams typically:
usernamescrapedAt — refresh on a 30–90 day cadenceSee Related Thunderbolt tools below for same-publisher companions you can chain without leaving the Scrapy.io billing account.
Most production deployments follow the same shape:
postUrl, placeId, videoId, reviewId, …) plus scrape date where history mattersInstagram Profile Bulk Extractor separates successful rows from per-input errors, so staging logic can WHERE type != 'error' (or the equivalent filter for your tool) without failing the whole batch. Join across Thunderbolt tools on those stable keys to build multi-step datasets without re-scraping upstream steps.
Maintaining Facebook, LinkedIn, Instagram, or X extractors in-house means handling rate limits, HTML or API changes, proxy rotation, and observability — work that rarely differentiates your product. Instagram Profile Bulk Extractor on Scrapy.io outsources that operational burden: you supply inputs, Scrapy.io runs the job, and you pay per successful row.
Thunderbolt listings add API-first, warehouse-ready documentation (clear caps, field lists, and pipeline patterns) so data teams can onboard without reading executor source code. When requirements change, update the input JSON or schedule — not your scraper fleet.
Instagram Profile Bulk Extractor runs on Scrapy.io support multiple ways to get data out:
For production pipelines, most teams land JSON in object storage, normalize in dbt or Spark, and schedule recurring runs so the Store listing becomes just another data source — not a manual step.
Run Instagram Profile Bulk Extractor once from the Store to validate inputs, then promote the same JSON payload to a scheduled job on Scrapy.io. Common patterns:
thunderbolt.p.scrapy.io on a queueThunderbolt tools use pay-per-result billing, so scheduled jobs stay predictable when you cap maxResults, max_posts, max_comments, or equivalent limits in the input form.
curl -X POST "https://thunderbolt.p.scrapy.io/instagram-profile-scraper/v1/api" \
-H "Content-Type: application/json" \
-H "X-API-Key: YOUR_API_KEY" \
-d '{
"usernames": ["nike", "natgeo"]
}'Bulk runs via the scraper endpoint:
curl -X POST "https://thunderbolt.p.scrapy.io/instagram-profile-scraper/v1/scraper" \
-H "Content-Type: application/json" \
-H "X-API-Key: YOUR_API_KEY" \
-d '{
"usernames": ["nike", "natgeo"]
}'Open the API tab on the Store listing for Python, JavaScript, cURL, OpenAPI, and MCP snippets.
Instagram Profile Bulk Extractor is available through the Scrapy.io MCP server — configure your API key in Cursor, Claude Desktop, or another MCP client, then invoke the tool from agent workflows. This is useful for ad-hoc research ("scrape these ten URLs and summarize the Output") without writing boilerplate HTTP code.
For production, prefer the publisher API or scheduled runs; use MCP for exploratory analysis and internal tooling where a human or agent supplies inputs interactively. See the API tab on Instagram Profile Bulk Extractor for MCP connection snippets.
| Tool | Best for |
|---|---|
| LinkedIn Profile Lead Scraper | Thunderbolt companion tool — overview |
| X Profile Insights Extractor | Thunderbolt companion tool — overview |
| X Profile Posts & Replies Collector | Thunderbolt companion tool — overview |
Batch usernames in API jobs for enrichment queues
Index warehouse tables on username for deduplication
Start with small batches to validate field shape in Output preview
Inspect per-row errors in the Errors output view instead of failing an entire batch
Facebook-heavy runs failing in a pattern? Use Issues on this Thunderbolt listing and attach your run ID plus one post, page, or search query
Instagram Profile Bulk Extractor collects publicly available data only. You are responsible for complying with platform terms, applicable laws, and data-protection regulations (including GDPR when personal data is involved). Consult your legal team for your specific use case.
Yes. Use webhooks, scheduled runs, or the publisher API to push data into your warehouse, CRM, or automation stack.
Yes. POST to https://thunderbolt.p.scrapy.io/instagram-profile-scraper/v1/api with your API key. See the API tab on the Store listing for ready-made snippets.
Yes. Configure the Scrapy.io MCP endpoint with your API key to query Instagram Profile Bulk Extractor from AI assistants and agent workflows.
Thunderbolt focuses on Meta and social discovery workflows — leave a Reviews note if this actor saved you from browser scraping and which Facebook surface you use daily.