Instagram Post & Reel Details Scraper · No Login

Get full details from any Instagram post or Reel by URL — no login, no cookies, no browser. This Instagram post scraper returns 128 structured fields per post, including likes, comments, views, shares, saves, reposts, captions, audio metadata, video URLs, and creator profiles — and it is the only Apify scraper that returns repost_count. Bulk URL input, with JSON/CSV/Excel export.

Watch the demo

What this Actor does

The Actor takes one or more public Instagram post, Reel, or TV URLs (or shortcodes/media IDs), fetches each media item's public details, refreshes the engagement counters from the creator's recent feed where a fresher value exists, and writes one analysis-ready dataset row per distinct post. An internal ML-embedding field from the source payload is removed before a row is saved, and every row carries a metrics_availability object so you can tell a genuinely unavailable metric from a real zero.

No Instagram account, cookie, proxy, or login token is requested in the input form. The Actor reads public data only.

What you can do with it

• Content performance analysis — compare engagement across photo, carousel, and Reel formats, and find which formats actually drive saves and reposts.
• Competitor benchmarking — pull complete metrics from a competitor's top posts, plus their caption, hashtag, and audio choices.
• Influencer campaign verification — check real engagement on sponsored posts using the is_paid_partnership flag and view-to-follower ratios.
• Trending audio discovery — extract audio metadata from viral Reels and build a library of trending sounds before they peak.
• UGC and brand monitoring — track posts that tag your brand or a location and measure earned media value.
• Ad creative research — analyze competitors' paid posts for format, caption length, hashtag usage, and engagement patterns.

Input

Field	Type	Required	Default	Description
postUrls	array of strings	No	["DVEGQskiMcy"]	Instagram post/Reel/TV URLs, shortcodes, or media IDs. Paste one per line for bulk runs.
postCode	string	No	—	Legacy single-value input. Prefer postUrls so multiple posts run in one run.

Accepts any public Instagram post URL — standard posts (/p/), Reels (/reel/), and TV (/tv/). At least one post is required; empty input returns a single error row explaining missing_required_post_code.

Example:

{
  "postUrls": [
    "https://www.instagram.com/p/DVEGQskiMcy/",
    "https://www.instagram.com/reel/XYZ789/"
  ]
}

Bulk runs are more economical

Batching many URLs into one run usually reduces the effective per-post overhead, because Apify charges a small Actor-start event each time a run begins. The Actor processes bulk input with balanced request pacing and emits at most one row per distinct post, even if two inputs resolve to the same media.

Output

Each dataset row is one post's public detail record. Rows contain:

• Post identity: post ID, shortcode (code), URL, and post type (photo / video / carousel / Reel).
• Engagement metrics: like_count, comment_count, view_count, play_count, share_count, save_count, and repost_count when the source exposes them.
• Metric availability: a metrics_availability object with available / currently_unavailable for share_count and save_count. currently_unavailable means the count is not published for that post — it does not mean zero. Shares and saves are frequently unavailable for images and carousels.
• Content: caption, hashtags, mentions, tagged users, location, and media/thumbnail URLs.
• Audio and music (Reels): audio title, artist, audio ID, original-audio flag, and genre.
• Creator profile: username, full name, user ID, verification state, follower count, biography, and profile picture.
• Technical metadata: posted/taken_at timestamps, media dimensions, video duration, is_paid_partnership, sponsor/product tags, and filter type.

A request that fails is still written as a row with success: false, the requested postCode, and an error code (for example failed_to_fetch_post_details or empty_post_payload), so you can separate failures from content. Missing optional source fields stay null rather than being guessed.

Example output (representative subset)

{
  "post_id": "3412567890123456789",
  "shortcode": "DAbc123XyZ",
  "post_url": "https://www.instagram.com/p/DAbc123XyZ/",
  "post_type": "Reel",
  "caption": "New collection just dropped 🔥 Link in bio #fashion #newdrop",
  "hashtags": ["fashion", "newdrop"],
  "mentions": ["@brandpartner"],
  "like_count": 45230,
  "comment_count": 1892,
  "view_count": 1240000,
  "share_count": 3400,
  "save_count": 8900,
  "repost_count": 420,
  "play_count": 1240000,
  "posted_at": "2026-05-15T14:30:00Z",
  "audio_title": "Original Audio",
  "audio_artist": "brandname",
  "is_original_audio": true,
  "is_paid_partnership": false,
  "video_duration": 28.5,
  "owner_username": "brandname",
  "owner_is_verified": true,
  "owner_follower_count": 2400000,
  "metrics_availability": {
    "share_count": "available",
    "save_count": "available"
  }
}

Fields shown are a representative subset of the 128 total fields returned per post. Field names follow Instagram's public post payload.

Pricing

This Actor is billed per dataset row (result) plus the standard Apify Actor-start event. From $1.50 per 1,000 results at the Gold subscription tier; the exact price is always shown in the Pricing section above. You only pay for the rows the run produces.

Example tasks

Ready-made configurations you can run as-is from the Actor's Example tasks tab:

• Build a performance snapshot from a competitor's top posts
• Track a creator's Reels and their audio over time
• Measure engagement on a branded hashtag campaign
• Compare saves and reposts across photo, carousel, and Reel formats

FAQ

How much does it cost to scrape Instagram post details? Pricing is per returned row, from $1.50 per 1,000 results, plus a small Actor-start event per run. A single-post test run costs a fraction of a cent.

Do I need cookies or a login? No. This Actor reads public data only — no cookies, no account, and no browser automation.

Can I scrape a Reel by URL? Yes. Paste any public /reel/ URL into postUrls. Standard posts (/p/) and TV (/tv/) are supported too.

Why are share_count or save_count sometimes missing? Those counters are not published for every post. When a count is unavailable, metrics_availability reports currently_unavailable instead of a misleading zero.

Can I scrape many posts in one run? Yes — paste one URL per line into postUrls. Bulk runs are usually more economical than one run per post.

Can I schedule it? Yes. Run it on an Apify schedule or from the API, and export results as JSON, CSV, Excel, or XML.

Related actors

More Instagram scrapers from the same portfolio:

Actor	What it does
Instagram Profile Posts & Reels Scraper	Every post and Reel from any profile
Instagram Profile Reels Scraper	All Reels from a profile with play counts and audio
Instagram Comments Scraper	Comments and replies from any post or Reel
Instagram Likes Scraper	Users who liked any post, with optional enrichment
Instagram Reposts Scraper	Profile repost history
Instagram Search Reels	Search Reels by keyword
Instagram Audio & Trending Sounds Scraper	Trending sounds and audio metadata
Instagram Hashtag Posts & Reels Scraper	Posts and Reels for a hashtag

Limits

• Processed in bounded concurrency; very large bulk lists finish in batches within the run timeout.
• At most one output row per distinct post — duplicate URLs or shortcodes resolving to the same media are de-duplicated.
• Metrics reflect what the public source exposes at run time; some counters are intermittently unavailable (see metrics_availability).
• The Actor keeps a restart-safe checkpoint so a platform migration does not re-emit (or re-charge for) already-written posts.

Automation

Use the Actor from code with the Apify API, schedule it, or trigger it by webhook. Results export to JSON, CSV, Excel, or XML and connect directly to Google Sheets, Slack, Zapier, Make, n8n, and other Apify integrations. Run it on a schedule to build a rolling time series of post and Reel engagement.

Feedback and support

Found a bug or need a slightly different output shape? Open an issue on the Issues tab. We aim to respond within 24 hours.