Instagram Likes Scraper

Export visible liker rows from public Instagram posts and Reels with Instagram Likes Scraper. Each row includes profile identity and the requested post URL for audience research, influencer vetting, and overlap analysis.

Public post visibility is not anonymous liker-list access. Instagram may require login to see who liked a public post. A confirmed login/signup gate produces an actionable warning, no liker rows for that target, and login_required in SUMMARY; the run continues with other inputs, even when failOnPrivateOrBlocked is true. This does not mean the post has zero likes or that anonymous access was restored. The existing start fee may still apply to a started run with no output; pricing is unchanged.

Your own optional authorized sessionCookie may help, but an expired or restricted session can still be gated. Access is not guaranteed. Never paste or share session secrets in logs or tasks. No operator session is supplied. Challenges, unknown blocking, parser/route errors, crashes, timeouts, unresolved shares and storage/billing failures are not converted into successful login warnings.

Quick start

Paste public post, Reel or Instagram share URLs, choose a small per-post limit, and start the Actor. Download available results from the dataset as JSON, CSV, or Excel.

{
  "postUrls": ["https://www.instagram.com/p/DLm63qQpxvw/"],
  "maxLikesPerPost": 10,
  "failOnPrivateOrBlocked": false
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Analyze Visible Likers on an Instagram Post
• Compare Visible Likers Across Instagram Posts
• Export Instagram Post Likers to a Dataset

What you get

One saved row per visible liker associated with a requested public media target, with available profile identity fields and post provenance. These are observed audience slices rather than full profiles or complete liker lists. SUMMARY records aggregate saved, loginRequired, blocked, unavailable, empty, partial and pending targets separately. postResults identifies each processed target by inputIndex and canonical postUrl, with reason (collected, login_required, unavailable, blocked, extraction_unconfirmed or route_failure) and saved row count. A login-gated target has no collected liker records, not a measured zero like count.

Who is it for?

• Creator-marketing researchers reviewing visible audiences of selected public posts.
• Social-media analysts keeping target-linked observations for manual review.
• Agencies comparing their own exported audience samples before campaign research.
• Data teams joining observed liker IDs while preserving which post exposed each row.

How you can use the data

• Review one known public post's visible slice. Use the supplied DLm63qQpxvw post with a ten-row per-post cap and anonymous access. Keep liker ID, username and requested post URL together, without assuming that the displayed like count promises accessible rows.
• Compare your own audience exports. Join id across post_url values in your own tool, retaining the target relationship for every row. The Actor does not calculate overlap, rank audiences or replace hidden liker data with comments or followers.
• Keep visibility labels in context. Read visible and partial_visible as descriptions of the returned slice. A total-like count or visible label does not verify whole-list completeness, and optional profile activity fields are not separate enrichment.
• Review incomplete collection before reporting absence. Check SUMMARY for run-level loginRequired, blocked, unavailable, empty, partial and pending targets and per-target postResults. Access challenges do not establish privacy or deletion, and a five-minute timeout can leave later targets unattempted.

Input settings

Setting / API key	Description
Post or Reel URLs — postUrls	Required list of public post, Reel or share URLs. Supported forms and resolution behavior are described below.
Maximum visible likers — maxLikesPerPost	Per-post limit from 1 to 1,000. Default 100, form example 10.
Optional session — sessionCookie	Your own optional authorized secret may help. Public posts can require login for likers; expired/restricted sessions may still produce warnings and no rows. Never share secrets in tasks/logs.
Proxy configuration — proxyConfiguration	Direct by default. Optional explicit settings for the customer-session route. See field help for scope and choices.
Profile detail enrichment — includeProfileDetails	Not available. True only displays a warning, without changing saved rows.
Stop on unavailable access — failOnPrivateOrBlocked	Default false. True fails other unavailable targets, but confirmed login/signup gates always warn and continue. Unknown blocks and real route/system failures remain failures with either value.

Supported forms are /p/, /reel/, /reels/ and /tv/ links, optionally username-prefixed, with carousel, embed or comment suffixes; and /share/TOKEN, /share/p/TOKEN or /share/reel/TOKEN links. Hosts are instagram.com, www.instagram.com, m.instagram.com and instagr.am. Share links use bounded anonymous resolution. Resolving a target does not guarantee access to its liker list. If a share cannot be resolved, supply its direct post URL. Usable entries are processed first; SUMMARY records unresolvedShares, unresolvedShareIndexes and reasons, then the run fails so unresolved shares cannot appear as successful empty lookups. Saved rows remain available. App deep links are unsupported.

Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

Output data

Illustrative shape only, not a claimed extraction result or a complete profile record:

{
  "id": "<profile-id>",
  "username": "<visible-handle>",
  "full_name": "<visible-name>",
  "is_private": false,
  "is_verified": false,
  "profile_pic_url": "https://example.invalid/profile-image.jpg",
  "liked_post": "https://www.instagram.com/p/DLm63qQpxvw/",
  "post_url": "https://www.instagram.com/p/DLm63qQpxvw/",
  "source_post_id": "<source-media-id>",
  "scraped_at": "2026-10-25T00:00:00.000Z",
  "page": 1,
  "visibility_status": "visible"
}

More output fields

Fields	Meaning
id, username, full_name	Visible liker identity. Names may be empty when not exposed.
is_private, is_verified	Profile-state flags from the visible response.
profile_pic_url, profile_pic_id	Visible profile-image references when exposed.
is_new, latest_reel_media, latest_reel_media_utc	Source activity fields. May be empty or unavailable, not separate profile enrichment.
liked_post, post_url, source_post_id	Requested post provenance. Use id to compare audiences across posts.
total_likes	Total count when exposed, not a promise of that many exported rows.
page, scraped_at, visibility_status	Source page, UTC save time, and visible or partial_visible.

The SUMMARY key-value record contains run-level saved, blocked, unavailable, empty, partial and pending counts/targets. It is not a per-post diagnosis, and blocked access is not proof of privacy or deletion. Unavailable inputs produce no fabricated dataset rows. visible describes the returned slice, not verified completeness of the whole liker list.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The start event is charged once when a valid run begins, even if no rows become available. The result event is charged for each target-bound visible liker row saved, with no result-row charge when no rows are saved.

Begin with a few URLs and a small per-post cap. See the live Pricing tab for current rates.

Tips for best results

• Start with one public media URL and a small per-post cap. A public post or like count does not promise accessible liker rows.
• Retain the requested post with each profile ID. Audience comparison needs that relationship rather than an unqualified combined profile list.
• Inspect summary pending targets before calling a batch complete. The five-minute timeout can leave work unattempted.
• Treat optional profile fields as source observations. The profile-detail setting currently warns rather than enriching output.
• Keep any authorized session secret outside shared materials. Never include cookies in public examples, shared tasks, support messages or exports.

Limits and caveats

Instagram can expose only a recent slice, require sign-in or challenge liker access. No complete-list or performance guarantee is made. Public posts and visible total counts do not guarantee anonymous rows. Returned order follows the source within each post, with no audience sorting.

Anonymous access is used when no cookie is supplied. A customer may optionally provide their own authorized sessionCookie for that run's public-media access. No operator session is supplied, and an accepted session can expire or be challenged. Never place cookies in public examples, shared tasks, support messages or exported data. Do not provide passwords or browser storage state.

Only visible liker fields for requested public media are collected. Full profiles, follower lists, direct messages and private likes are outside scope. includeProfileDetails currently adds only a warning and does not change saved rows. Unavailable targets produce no fabricated content rows, and SUMMARY is a run-level record rather than a per-post diagnosis.

Optional identity, image and activity fields can be empty or absent. Visibility labels do not verify completeness. The five-minute timeout can leave pending targets, and blocked access alone does not establish privacy or deletion. Any overlap analysis, audience ranking or repeated-export comparison is your own downstream work.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~instagram-likes-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "postUrls": [
    "https://www.instagram.com/p/DLm63qQpxvw/"
  ],
  "maxLikesPerPost": 10,
  "failOnPrivateOrBlocked": false
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/instagram-likes-scraper').call({
  "postUrls": [
    "https://www.instagram.com/p/DLm63qQpxvw/"
  ],
  "maxLikesPerPost": 10,
  "failOnPrivateOrBlocked": false
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/instagram-likes-scraper').call(run_input={'postUrls': ['https://www.instagram.com/p/DLm63qQpxvw/'], 'maxLikesPerPost': 10, 'failOnPrivateOrBlocked': False})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with Instagram Likes Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Instagram Likes Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/instagram-likes-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Instagram Likes Scraper by Fetch Cat, or give it the identifier fetch_cat/instagram-likes-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Instagram Likes Scraper to collect up to 5 visible liker rows for https://www.instagram.com/p/DLm63qQpxvw/ anonymously, with stop-on-unavailable off. Keep liker IDs and requested-post links without claiming the complete audience.”
• “Retrieve up to 3 visible liker rows for the same DLm63qQpxvw public post anonymously, with profile enrichment off and stop-on-unavailable off. Show available names and visibility labels, leaving missing fields unknown.”
• “Collect up to 5 visible liker rows from the same public post anonymously, with stop-on-unavailable off. Keep profile IDs, post provenance and save times for my own comparison, and report aggregate pending or unavailable targets without assigning a per-post diagnosis.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I export Instagram likes without login?

Anonymous access is supported but Instagram often hides the liker list. A public count does not guarantee anonymous rows. Your own optional session may improve access but does not guarantee results.

Can I use this as an Instagram likes API?

Yes, through Apify's API or MCP. It is not an official Instagram API, and returns only the visible rows available for the requested media.

Why did I get no rows?

Instagram may not have exposed a usable liker list. Review the run summary. Inaccessibility does not establish that the post is private or deleted.

Does it export full profiles, followers, DMs, or private likes?

No. It exports visible liker fields on public media. includeProfileDetails currently adds no enrichment. For profile research, consider the related profile Actor below.

Can I export to CSV or compare audiences?

Download the dataset in CSV, JSON or Excel. Compare id values across post_url values in your own tool. Overlap scores are not calculated by this Actor.

Related Actors

• Instagram Profile & Posts Scraper — Collect public profile details and available post or Reel metadata from known accounts or media URLs.
• Instagram Stories & Highlights Scraper — Collect accessible story and highlight records using your own authorized Instagram session. This does not bypass private-profile permissions.
• Instagram Post Details Scraper — Collect available captions, author details, dates and visible engagement from known public post URLs.
• Instagram Related Profiles Scraper — Collect direct related-profile suggestions from seed accounts, with available public identity fields.
• Instagram AI Transcript Extractor — Retrieve available transcript text from known public Instagram Reel or video URLs.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥

Invalid post links

Use a direct /p/, /reel/, /reels/, or /tv/ URL, optionally prefixed by a username (for example /example.user/reel/CODE/). Both query-style /?img_index=1 and recognized path-style /img_index=1 carousel links are accepted. For liker lookup these normalize to the canonical post URL, preserving the exact case-sensitive shortcode; carousel selection does not change the post's liker list. /share/TOKEN, /share/p/TOKEN and /share/reel/TOKEN links are supported through bounded trusted-host resolution; view suffixes identify the same whole post. Unresolved shares remain explicit failures after usable entries are processed. App deep links are unsupported. The Console and API reject wrong hosts/protocols and non-post paths before startup. Local runs or other paths that bypass schema validation skip invalid entries with warnings and report their zero-based positions in SUMMARY.invalidPostIndexes. Valid entries continue normally. If every entry is invalid, extraction is not attempted and the Actor does not charge its start or result events.