Instagram User ID Scraper

Instagram User ID Scraper

📍 What is Instagram User ID Scraper?

Instagram User ID Scraper resolves Instagram's stable numeric user IDs into the current profile name and canonical profile URL — in bulk, with no Instagram login required. Give it one or many numeric IDs, and every ID that still resolves comes back as a clean row: the @username and its profile_url.

Compared with opening each profile page and copying the handle by hand, this turns the lookup into a repeatable, batch, structured export — resolved IDs come back as clean rows you can sort, filter, and re-run at any time.

What can you use it for?

• Enrich datasets that only have IDs: turn numeric Instagram user IDs from exports, CSVs, or third-party tools into readable usernames and clickable profile links.
• Build or repair contact lists: resolve a batch of IDs into @username + profile URL in one run, ready to paste into outreach or CRM.
• Reconcile duplicate records: two rows that reference the same account under different IDs both resolve to the same @username, so deduplication gets easier.
• Audit public accounts at scale: batch-check which IDs still resolve to a public profile by comparing your input list against the rows that come back.
• Keep names current: re-run the same ID list later to pick up renamed accounts — every run re-reads the account's current public username, so a rename shows up on the next run.
• Feed downstream workflows: use the resolved username and URL in CRM, monitoring, or reporting, driven via the REST API or MCP.

What data does it extract?

To make the most of a batch, Instagram User ID Scraper gives you:

• Clean, structured rows — every resolved ID returns a consistent profile_id, profile_name, and profile_url record.
• 8 export formats — CSV, JSON, JSONL, XLSX, XLS, XML, HTML, RSS.
• Integrations — webhook callbacks, MCP, n8n workflows, and the CoreClaw REST API.
• Anonymous access — no Instagram account or login required.

⬇️ Input

Instagram User IDs (required) — profile_ids

The list of numeric Instagram user IDs to resolve into profile_name and profile_url. In the CoreClaw UI this is a request list — add one numeric ID per row.

Recommended: positive numeric IDs only (Instagram's internal account IDs, the kind third-party tools and exports hand you). Mix a few IDs to see the batch behavior across accounts.

Not supported: profile names (@instagram), profile URLs, media IDs, or shortcodes — the resolver only accepts positive numeric account IDs. If you only have usernames, convert them to numeric IDs first.

Format: one numeric ID per row in the request list, or an array of IDs.

Example:

The snippet below is the run input (the input.parameters.custom payload):

{
  "profile_ids": ["25025320", "173560420", "528817151"]
}

⬆️ Output

Results appear in a table with the three columns above — one row per resolved ID. You can sort, filter, and export them.

🧩 Full JSON record

[
  {
    "profile_id": "25025320",
    "profile_name": "@instagram",
    "profile_url": "https://www.instagram.com/instagram/"
  }
]

❓ FAQ

How does it work?

It reads Instagram's public profile metadata anonymously — no login required. Send it numeric user IDs and it returns each account's current username and profile URL.

Can I resolve many IDs at once?

Yes. The input is a batch — add one ID per row or pass an array of IDs. Every resolved ID returns its own row.

What inputs does it accept?

Only positive numeric account IDs. Profile names, profile URLs, media IDs, and shortcodes aren't supported — if you only have usernames, convert them to numeric IDs first.

What happens if an ID can't be resolved?

An ID that fails to resolve or yields no valid data simply returns no result — this typically applies to deleted, suspended, restricted, or nonexistent accounts. No-result IDs aren't billed; you only pay for successfully resolved results.

Does it need my Instagram login?

No. It reads Instagram's public metadata anonymously and never signs in — your Instagram account is never used.

Can I integrate it with other apps?

Yes. Results export in 8 formats — CSV, JSON, JSONL, XLSX, XLS, XML, HTML, RSS — and the platform supports webhook callbacks, MCP, and n8n workflows.

Can I use it as an API?

Yes. Use the CoreClaw REST API to run it programmatically.

The base URL is https://openapi.coreclaw.com, all paths start with /api/v2, and you authenticate with Authorization: Bearer YOUR_API_KEY (the legacy api-key header and ?token= query still work).

Typical flow:

1. GET /api/v2/workers/{workerId}/input-schema to fetch the input schema (or GET /api/v2/workers/{workerId} for full details). workerId is a slug or owner~name path; version defaults to latest.
2. POST /api/v2/workers/{workerId}/runs to start a run — pass is_async, and put the scraper input in input.parameters.custom. Set a callback_url to receive a callback instead of polling.
3. Save the returned data.run_slug.
4. GET /api/v2/worker-runs/{runId} to check status (use the run_slug as {runId}).
5. GET /api/v2/worker-runs/{runId}/result for the result, or /result/export for a file export.

Is resolving Instagram usernames legal?

This worker only reads public account metadata and never accesses private accounts. Use it in ways that respect Instagram's terms and the privacy and data regulations that apply to you; don't use it to obtain private account data.

Feedback

Found a bug, or want a new output field? We'd love to hear from you — reach out at support@coreclaw.com.