Pricing

from $0.30 / 1,000 per comment returneds

Try for free

Go to Apify Store

Instagram Comments Scraper - Date Filter & New-Comment Monitor

Try for free

From $0.30 per 1,000. Scrape top-level comments on any public Instagram post or reel: text, GIF, likes, timestamp, commenter username, ID and verified badge. No login or cookies. Comments come back newest-first, so a date filter or the built-in monitor pulls only new ones. Replies not included.

Pricing

from $0.30 / 1,000 per comment returneds

Rating

0.0

(0)

Developer

Scrapers Delight

Actor stats

Bookmarked

Total users

Monthly active users

5 days ago

Last modified

Categories

Social media

Lead generation

Automation

Instagram post / reel URLs

startUrls

Optional

The posts whose comments you want. Paste any public post, reel or IGTV URL — https://www.instagram.com/p/DZ5T2XPllXv/, https://www.instagram.com/reel//, https://www.instagram.com/tv// — with or without tracking parameters. All three media types were verified live (image, carousel and video/reel posts all resolve). This Actor reads ONE post's comment stream per URL: it does not crawl a profile, a hashtag or an explore feed, and instagram.com/share/ redirect links are rejected rather than guessed at. Leave empty and it runs the documented sample so an empty input still returns rows.

Type:array

…or bare shortcodes

shortcodes

Optional

The same thing without the URL: DZ5T2XPllXv, DWy2NsDD7CE. Handy when your post ids come out of a spreadsheet or another Actor. Mixed with the URL list above; duplicates are collapsed.

Type:array

Max comments per post

maxCommentsPerPost

Optional

Stop after this many delivered comments on each post. 0 = the whole top-level thread. Instagram serves ~13-15 comments per call whatever page size is asked for (measured: first=12, 24, 50 and 100 all returned 14 edges), so a 2,118-comment post is 148 calls / ~106 s and a 397-comment post is 28 calls / ~19 s. Keep a cap on unless you mean to pull an entire thread.

Type:integer

Minimum:0

Maximum:500000

Default:50

Max comments scanned per post

maxCommentsScannedPerPost

Optional

The WORK bound, as opposed to the delivery bound above. A filter or a date window drops a comment AFTER it has been read, so 'give me the 10 comments mentioning "discount"' can mean reading a 79,000-comment thread to find them. This caps how many comments the Actor will READ per post. 0 = automatic (recommended): no budget at all when nothing can drop a row, and otherwise 100 comments read per row you asked to be delivered — floor 1,000, ceiling 20,000. Measured A/B on one input (a filter matching nothing on a 2,118-comment thread, at maxCommentsPerPost: 10 so the budget is its 1,000 floor, both builds run at the same moment): without the budget 2,119 comments were read over 148 calls in 113 s and 0 delivered; with it, 1,009 read over 72 calls in 38 s and 0 delivered — same result, 2.7x less work. The budget is proportional to the rows you asked for, so it bites hardest where the waste is biggest and not at all on a thread smaller than it: re-measured on that same input at the DEFAULT maxCommentsPerPost: 50 the budget is 5,000, it never trips on that 2,118-comment thread, and the whole thread is read (2,119 comments, 0 rows, $0 charged, scanBudgetReached false — run DFYxmxcpJdiOKsghL, build 0.2.12). Set a number to override; set 500000 for effectively no budget. It is checked at a page boundary, so it can overshoot by one page (~13-15 comments) in your favour. Comments read are NEVER billed — only comments delivered are — and when this stops a post the run says so, names the filter and names this field.

Type:integer

Minimum:0

Maximum:500000

Default:0

Max comments in total

maxComments

Optional

Overall ceiling across every post in this run. 0 = no overall ceiling. Useful when you paste 200 URLs and want to bound the bill rather than each post.

Type:integer

Minimum:0

Maximum:500000

Default:0

Only comments newer than

commentsNewerThan

Optional

THE POINT OF THIS ACTOR. A date (2026-09-01), a timestamp (2026-09-01T12:00:00Z) or a span ("7 days", "48 hours", "2 weeks"). Instagram serves this comment stream strictly newest-first — 0 inversions of created_at across 3,189 comments on 18 posts, measured 2026-09-07 — so the crawl STOPS at the boundary instead of pulling the thread and filtering afterwards. On a 79,000-comment post, "yesterday" costs you a handful of calls and a handful of rows, not 79,000 of each. Comments older than the bound are never delivered and never billed.

Type:string

Example:

7 days

Only comments older than

commentsOlderThan

Optional

The other edge of the window, same formats. Comments newer than this sit at the head of the stream and are skipped without being delivered or billed. Use both bounds to pull, say, only the comments posted during a giveaway window.

Type:string

Example:

2026-09-01

Grace pages past the date boundary

dateBoundGracePages

Optional

How many extra pages to read after the stream first crosses the "newer than" boundary, before stopping. Reverse-chronological order measured clean (0 inversions in 3,189 comments), so 1 is plenty of insurance; raise it if you would rather pay for a few more calls than risk a straggler. 0 stops immediately at the boundary.

Type:integer

Minimum:0

Maximum:10

Default:1

Monitor mode — only comments new since the last run

monitorMode

Optional

Schedule this Actor and each run delivers ONLY the comments posted since the previous run. The last-seen comment id per post is kept in a NAMED key-value store ('instagram-comments-monitor-state'), so paging stops exactly at it — no dedupe heuristics, no re-billing of comments you already have. Adds a flat monitor fee per run (see Pricing), charged only if Instagram actually answered.

Type:boolean

Default:false

Watch name

monitorStateKey

Optional

Optional label that separates one watch from another on the SAME post — e.g. run a 'support' watch and a 'giveaway' watch over the same URL without either resetting the other. Leave empty for the default watch.

Type:string

Example:

giveaway-oct

Comments to deliver on the first monitor run

monitorSeedComments

Optional

On the very first run for a post there is no last-seen id, so every comment would read as new. This bounds that seed run. 0 = record the baseline and deliver nothing, so your first real delivery is genuinely new comments only.

Type:integer

Minimum:0

Maximum:500000

Default:25

Send alerts for new comments

alertOnNewComment

Optional

In Monitor mode, push each new comment to the webhook / Slack / email sinks below. Alerts are billed only when a delivery actually succeeds, and never fire outside Monitor mode.

Type:boolean

Default:true

Webhook URL

webhookUrl

Optional

POSTed one JSON body per new comment: { event: 'new-instagram-comment', comment: {…the full row…}, scrapedAt }.

Type:string

Slack incoming-webhook URL

slackWebhookUrl

Optional

A Slack incoming webhook. Each new comment arrives as a card with the commenter, the verified badge, the like count and a deep link to the comment.

Type:string

Email recipients

emailRecipients

Optional

One digest email per monitor run listing the new comments, sent through apify/send-mail. Billed as one alert per recipient, and ONLY when that send-mail run reports SUCCEEDED — a refused or failed send is never charged. Note apify/send-mail's own limits: on the Apify free plan it accepts only your own account address, and up to 20 recipients on a paid plan.

Type:array

Comment types to keep

commentTypes

Optional

GIF comments come back with text:"" and a Giphy payload — 268 of 3,189 comments measured (8.4%), and every single one carried a live GIF URL. Most scrapers in this lane ship them as blank rows; this one types them and fills gifUrl / gifId. 'empty' is the rare row with neither text nor a GIF (6 of 3,189). Rows dropped here are never billed.

Type:string[]

Default:

[
  "text",
  "gif",
  "empty"
]

Minimum likes on the comment

minLikeCount

Optional

Keep only comments with at least this many likes. 81% of measured comments had zero likes (609 of 3,189 had at least one), so even minLikeCount 1 is a strong signal filter.

Type:integer

Minimum:0

Default:0

Only verified commenters

onlyVerifiedCommenters

Optional

Keep only comments from blue-badge accounts. Measured 139 of 3,189 comments (4.4%) — a small, high-signal slice for PR and influencer work.

Type:boolean

Default:false

Comment text must contain any of

textIncludes

Optional

Case-insensitive substrings. A comment is kept if it contains ANY of them. Leave empty for no keyword filter.

Type:array

Example:

[
  "shipping",
  "price",
  "where can i buy"
]

…and none of

textExcludes

Optional

Case-insensitive substrings that disqualify a comment. Handy for stripping emoji-spam or a giveaway hashtag.

Type:array

Only comments containing an email address

requireEmailInText

Optional

Keep only comments where the commenter typed an email address. This reads what is IN the comment — it is not an email lookup or enrichment of any kind.

Type:boolean

Default:false

Only comments containing a link

requireLinkInText

Optional

Keep only comments containing an http(s):// or www. link.

Type:boolean

Default:false

Drop the post owner's own comments

excludePostOwnerComments

Optional

Removes the creator's own replies from the thread. Matched on the numeric account id, not the username, so it works even without the post-context fetch.

Type:boolean

Default:false

Only these commenters

onlyCommenters

Optional

Usernames to keep (with or without the @). Everything else is dropped before delivery.

Type:array

Exclude these commenters

excludeCommenters

Optional

Usernames to drop — your own brand account, known bots, a repeat spammer.

Type:array

Add post context + the coverage ledger

includePostContext

Optional

One extra fetch of the post's own page (736-947 KB measured, ~1.2 s) per post, which adds the owner's username, Instagram's OWN comment count, the like count, the caption, the posted-at date — and the coverage ledger: what share of the thread this run actually read. Nobody else in this lane tells you that. Billed once per post, only when the post produced rows. In Monitor mode leave it OFF: it re-fetches ~750 KB and a charge per post on every scheduled tick for information that barely changes.

Type:boolean

Default:true

Include the raw comment JSON

includeRawComment

Optional

Adds a rawComment column holding Instagram's untouched node object, for anyone who wants a field this Actor does not map. Roughly doubles the dataset size.

Type:boolean

Default:false

De-duplicate by comment id

deduplicateComments

Optional

On by default. 0 duplicate comment ids were measured across 3,189 comments and 228 paginated calls, so this is a belt-and-braces guarantee rather than a fix for a known problem — and de-duplication runs BEFORE billing, so a duplicate could never be charged twice.

Type:boolean

Default:true

Resumable pagination

resumeMode

Optional

For deep backfills of huge threads. The pagination cursor for each post is stored in a NAMED key-value store ('instagram-comments-resume-state'), so the next run with this switched on continues where the last one stopped instead of paying to re-read the head of the thread. Split a 79,000-comment post over several cheap runs. Ignored when Monitor mode is on — the two pull in opposite directions.

Type:boolean

Default:false

Reset the stored cursors

resetResumeState

Optional

Clears the saved pagination cursors so the next resumable run starts again from the newest comment.

Type:boolean

Default:false

Recover Instagram's query ids automatically

docIdRecovery

Optional

This route rides a Meta persisted-query id, and Meta rotates those on deploys. If EVERY post — including this Actor's own known-live sample — comes back empty, the Actor re-mints its session and then sweeps the post page's JavaScript bundles to recover the new ids and caches them, instead of exiting successfully with zero rows. Costs nothing on a normal run. Leave on unless you are debugging.

Type:boolean

Default:true

Max pages per post

maxPagesPerPost

Optional

Hard ceiling on paginated calls per post. 0 = no ceiling. One page is ~13-15 comments regardless of the page size asked for.

Type:integer

Minimum:0

Maximum:200000

Default:0

Max seconds per post

maxSecondsPerPost

Optional

Give up on one post after this long and move to the next, so a single enormous thread cannot eat a whole run. 0 = no per-post limit. The reason is recorded as truncationReason on the rows and in the run's POST_STATUS record.

Type:integer

Minimum:0

Maximum:86400

Default:0

Posts scraped in parallel

maxConcurrency

Optional

Pagination inside ONE post is strictly sequential (each page needs the previous page's cursor), so this parallelises across posts. 3 is a good default; 228 consecutive calls on one minted session measured 100% HTTP 200.

Type:integer

Minimum:1

Maximum:8

Default:3

Request timeout (seconds)

requestTimeoutSecs

Optional

Per-request timeout. Comment calls averaged 932 ms across 228 calls through an Apify datacenter proxy (710 ms on the sequential deep-pagination run), so the default is generous.

Type:integer

Minimum:5

Maximum:300

Default:45

Retries per request

maxRequestRetries

Optional

Retries on a timeout, a 429 or a 5xx. One transient proxy ECONNRESET was seen in ~350 calls — that is a retry, not a block.

Type:integer

Minimum:0

Maximum:8

Default:3

Rows buffered per post before streaming

maxBufferedCommentsPerPost

Optional

Rows are held until a post's crawl finishes so the completeness columns on every row are final. Past this many they are streamed out instead, and topLevelComplete / truncationReason / postCommentsScanned / topLevelCoveragePct are null on those rows rather than guessed — the run's POST_STATUS key-value record then holds the authoritative ledger. Only bites on threads of tens of thousands of comments.

Type:integer

Minimum:500

Maximum:200000

Default:20000

Proxy

proxyConfiguration

Optional

Apify Proxy, automatic (datacenter) group. Measured 2026-09-07 on the comment endpoint: datacenter 228/228 HTTP 200 at ~932 ms average, residential US 10/10 at ~1,049 ms. Datacenter is both faster and cheaper here, so it is the default; switch to RESIDENTIAL only if you start seeing 429s.

Type:object

Default:

{
  "useApifyProxy": true
}

Instagram Comments Scraper - Comments, Authors & Likes

zaver.api/instagram-comment-scraper

Scrape all comments from any Instagram post or reel - comment text, author (username, verified), likes, timestamp and reply count. Bulk post URLs, deep export, no login. $0.99 per 1,000 comments. Export CSV, JSON, Excel.

Zaver

Instagram Post & Reel Comments Scraper

monknwarriors/instagram-comment-scraper

Scrape every comment from any public Instagram post or reel — comment text, likes, timestamps, reply counts, and each commenter's username, ID, verified badge and profile picture. No login required.

Monk N Warriors

Instagram Comments Scraper - Fast & Filterable

orkait/instagram-comments-scraper

Scrape Instagram comments from any post or reel. Add post URLs and export comment text, author username, verified status, likes, reply count and timestamps to JSON, CSV or Excel. Filter comments by likes, date or keyword and sort them server-side before you pay for a row.

orkait

Instagram Comments Scraper

seemuapps/instagram-comments-scraper

Scrape all comments from any public Instagram post or Reel comment text, author profile, like count, and timestamp. Just paste the post URL.

Andrew

Instagram Comments Scraper

scrapesmith/instagram-comments-scraper

⚡ Instagram Comments Scraper – Extract comments, usernames, likes, replies & timestamps from any public post or reel. Bulk scraping, no login needed. Export to JSON, CSV or Excel. Starts at $0.50/1,000 results.

Scrape Smith

2.1K

4.4

Instagram Post Comments Scraper

data_direct/instagram-post-comments-scraper

Get the comments on a post or reel

Data Direct

Instagram Comments Scraper - Post & Reel Comments

dami_studio/instagram-comments-scraper

Scrape comments from a public Instagram post or reel. Replies sit under their comment, and both levels come back labelled. Every row has the author, the text, the time, likes and reply count. Nothing to log into, no cookie to paste. $0.40 per 1,000 rows.

Dami's Studio

Instagram Comment Scraper

herus13/instagram-comment-scraper

Scrape Instagram comments anonymously by post/reel URL (or by username for recent posts). Returns comment text, author, likes, replies, and timestamp. No login required.

bootforge

Instagram Comments Scraper 💬

scriptbase/instagram-comments-scraper

💬 Export Instagram comments to JSON, CSV or Excel. Get comment text, author handle, likes, reply count and date from any post or reel. Paginated, no login, no Instagram API access needed.

Scriptbase

Instagram Comments Scraper

toolzerhub/instagram-comments-scraper

Scrape every public comment on any Instagram post or reel, not just the first page. One row per comment with the text, author, like count, reply count and date. Sort by popular, recent or verified. No Instagram login needed.