Instagram Reel Scraper

Extract public Instagram Reel metadata from direct Reel URLs for creator research, campaign checks and repeatable data exports. Get visible captions, engagement metrics and media links in a dataset you can export to CSV, JSON or Excel. Instagram may hide many fields from logged-out visitors.

Quick start

1. Paste one public Reel URL into Instagram Reel URLs.
2. Set Maximum reels to 1 and start the Actor.
3. Open the dataset to inspect the result and its warnings, then export your chosen format.

{
  "startUrls": [{ "url": "https://www.instagram.com/reel/Da-2R72yymt/" }],
  "maxItems": 1
}

Use a currently available public Reel for your first test. A URL example is not a guarantee that Instagram still exposes that Reel. No login is used. If the main request is blocked or encounters a retryable network/server failure, the second of at most three requests tries the public Reel embed using the same connection settings. If that also fails and an anonymous page bootstrap is available, the final request uses Instagram's public logged-out data query instead of repeating the main page. Structured page, embed and query records must match the requested Reel and contain usable media links. No account cookies or login are used. Blocked or unavailable targets can produce diagnostic rows instead of Reel data.

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.

What you get

Public metadata or diagnostic rows for admitted unique Reel URLs, with canonical shortcode identity and any visible captions, owner fields, dates, counts and media links. Optional values can be null. Plays and views stay separately labeled, the share-count field remains null, and media URLs are not downloaded files.

Who is it for?

• Creator researchers reviewing metadata for known public Reel links.
• Campaign analysts keeping observed caption and engagement fields with source context.
• Content operations teams retaining available media references without file downloads.
• Data developers separating usable Reel rows from target-specific diagnostics and pending work.

How you can use the data

• Review one known Reel. Use the supplied Da-2R72yymt URL with a one-Reel cap. Keep shortcode, canonical URL, available caption and warnings together, allowing for the example no longer being publicly exposed.
• Keep plays and views distinct in reports. Preserve videoPlayCount and viewCount separately and leave missing values unknown. ShareCount is always null rather than evidence of zero shares, and not every absent field gets an individual warning.
• Reconcile a bounded campaign URL list. Use direct Reel URLs and an explicit unique-input cap. Duplicate shortcodes run once in input order, while per-URL diagnostics keep a failed target distinct from missing metadata on a saved Reel.
• Review or continue interrupted work deliberately. Inspect RUN_SUMMARY and a saved RUN_CHECKPOINT after a deadline stop. Resurrection uses the same run, input and storage. A separate run does not reuse the old checkpoint, and the Actor does not discover a profile's Reels for you.

Input settings

• Single Reel check: Use the quick-start input to inspect visible metadata and warnings.
• Batch campaign review: Supply several direct Reel URLs and set maxItems to the number you want processed. Duplicate shortcodes are processed once, in input order.
• Public-data troubleshooting: Keep warnings, error and errorDescription in your export. A blocked response alone does not show that a Reel is private or deleted.

More input configuration

Setting	JSON key	Behavior
Instagram Reel URLs	startUrls	Required list of direct public Reel URLs. Profile-prefixed Reel URLs are also accepted.
Maximum reels	maxItems	Process up to this many unique URLs, from 1 to 500. API default: 10. Form example: 3.
Maximum runtime	maxRuntimeSecs	Time budget from 31 to 270 seconds. Default 270. Leaves time to save progress.
Proxy configuration	proxyConfiguration	Optional settings used from the first request. Omission uses direct requests, with no automatic proxy fallback. See field help for details.

This Actor does not discover Reels from profiles, hashtags, audio or locations. It does not sort results by popularity. Custom connection settings remain optional. The quick start does not enable a proxy.

Example inputs

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

Output data

Field	Description
inputUrl, url	Original input and canonical Reel URL.
id, shortCode, type	Shortcode identity and the constant type reel. id is not a numeric Instagram media ID.
caption, hashtags, mentions	Visible caption text and the tags or mentions parsed from it.
ownerUsername, ownerId	Owner metadata when exposed.
timestamp	Publication timestamp when exposed.
likesCount, commentsCount	Public counts when visible.
videoPlayCount, viewCount	Separately labeled play and view counts. Plays are never copied into views.
shareCount	Reserved compatibility field. Currently always null.
thumbnailUrl, videoUrl	Public media links when exposed, not downloaded files.
dimensionsHeight, dimensionsWidth	Video dimensions when exposed.
warnings	Notes about missing fields and public visibility limits.
error, errorDescription	Diagnostic details for a blocked, unavailable or failed target.
fetchedAt	Time the row was created.

Example output

This abbreviated, shape-only example illustrates nullable fields, not a newly verified extraction result:

{
  "inputUrl": "https://www.instagram.com/reel/Da-2R72yymt/",
  "id": "Da-2R72yymt",
  "shortCode": "Da-2R72yymt",
  "type": "reel",
  "url": "https://www.instagram.com/reel/Da-2R72yymt/",
  "caption": null,
  "hashtags": [],
  "mentions": [],
  "ownerUsername": null,
  "likesCount": null,
  "commentsCount": null,
  "videoPlayCount": null,
  "viewCount": null,
  "shareCount": null,
  "warnings": ["Caption was not visible in the public response."],
  "error": null,
  "errorDescription": null
}

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. The item event charges for each successfully saved Reel row, while diagnostic rows are saved without that item charge. The unique-input cap limits URLs processed rather than guaranteeing complete metadata.

Optional proxy services can add charges. See the live Pricing tab for current rates and plan-specific pricing.

Tips for best results

• Use one current public Reel URL and a small cap first. A direct Reel may be available without appearing in a profile grid.
• Keep warnings and error fields when exporting. They describe response-supported limits rather than verified privacy or deletion.
• Treat null metrics as unknown. Plays are not copied into views, and share count is not populated.
• Use connection settings deliberately. Omission makes direct requests with no automatic proxy fallback.
• Inspect checkpoint context before resurrection. Continue only the same run with unchanged input and storage when using its saved progress.

Limits and caveats

Only direct public Reel URLs are accepted, including supported profile-prefixed Reel forms. There is no discovery from profiles, hashtags, audio or locations, popularity sorting, login cookies, private-account access, direct messages or video-file download.

Instagram can hide captions, metrics, owners and media links from logged-out views. Missing fields are not guessed, warnings are not exhaustive, and media links can expire. Shortcode identity is not a numeric media ID. Plays and views are separate values, and the share-count compatibility field remains null.

Invalid input URLs reject the input before extraction. Per-URL failures are isolated so other URLs can complete, while an all-error workload currently fails after diagnostic rows are saved. Read RUN_SUMMARY for response reasons rather than inferring that a target is private or deleted.

A deadline-limited run can save RUN_CHECKPOINT and preserve completed rows. Resurrect the same run with unchanged input and storage to continue. Starting a separate run does not reuse the checkpoint. Optional proxy settings apply from the first request and do not guarantee access or metadata completeness.

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-reel-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "startUrls": [
    {
      "url": "https://www.instagram.com/reel/Da-2R72yymt/"
    }
  ],
  "maxItems": 1
}
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-reel-scraper').call({
  "startUrls": [
    {
      "url": "https://www.instagram.com/reel/Da-2R72yymt/"
    }
  ],
  "maxItems": 1
});
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-reel-scraper').call(run_input={'startUrls': [{'url': 'https://www.instagram.com/reel/Da-2R72yymt/'}], 'maxItems': 1})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API usage notes

Use the returned defaultDatasetId to retrieve or export results. Run creation with cURL is asynchronous. Wait for the run to finish before reading its final dataset.

MCP and AI agents

You can ask your AI assistant to collect data with Instagram Reel 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 Reel 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-reel-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 Reel Scraper by Fetch Cat, or give it the identifier fetch_cat/instagram-reel-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 Reel Scraper to retrieve https://www.instagram.com/reel/Da-2R72yymt/ with a one-Reel cap and direct defaults. Show available caption, owner fields and warnings, leaving missing values unknown.”
• “Collect the same Da-2R72yymt Reel with a one-input cap and direct defaults. Keep play and view counts separately labeled, with share count unknown rather than zero, and retain source identity for my report.”
• “Retrieve the same known public Reel with a one-Reel cap and direct defaults. Make a review table of available media links and diagnostic fields without downloading the video or treating access failure as proof of privacy or deletion.”

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 scrape every Reel from a profile?

No. This Actor accepts direct Reel URLs, not profile-listing requests.

Why are fields empty?

Logged-out public pages may omit fields. null is not a zero count. Warnings and diagnostic rows describe only what the response supports.

Can I download the video?

The Actor returns a videoUrl when visible, not a binary video file. Media URLs may expire.

Related Actors

More Instagram scrapers

• Instagram Likes Scraper — Collect visible liker profiles from known public posts or Reels when Instagram exposes the list.
• 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 Mentions Scraper — Collect public media that tags a target profile, with available media and author fields.

• TikTok Video Scraper — short-form video data from TikTok 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. ♥