Instagram Hashtag Scraper
Pricing
from $1.10 / 1,000 item processeds
Instagram Hashtag Scraper
Export visible public Instagram hashtag cards with post and reel links, caption text, author hints, hashtags, mentions and thumbnails. Anonymous coverage varies.
Pricing
from $1.10 / 1,000 item processeds
Rating
0.0
(0)
Developer
Fetch Cat
Maintained by CommunityActor stats
0
Bookmarked
8
Total users
3
Monthly active users
7 days ago
Last modified
Categories
Share
Export visible public Instagram post and reel cards for one or more hashtags. Instagram Hashtag Scraper returns media links, visible caption text, author hints, hashtags, mentions and thumbnails for content research and campaign snapshots—not complete post details or a guaranteed recent feed.
Anonymous access varies: a hashtag can return fewer cards than requested, no cards, or an access error. No Instagram login or cookies are required or accepted.
Quick start
- Enter a hashtag such as
cats,#nature, or an Instagram hashtag URL. - Start with a small per-hashtag limit:
{"hashtags": ["cats"],"maxItemsPerHashtag": 10}
- Click Start, then open the dataset to inspect the cards and export JSON, CSV or Excel. Missing visible information may be
null.
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:
What you get
Visible public post and Reel cards with media links, shortcodes and available caption text, author hints, tags and thumbnails. Each row keeps the requested hashtag, source page, position and collection time. This is a card snapshot rather than a full post, exact engagement report or guaranteed recent feed.
Who is it for?
- Social-listening researchers reviewing public card samples for selected hashtags.
- Content agencies assembling source-linked visual and caption references.
- Campaign analysts comparing their own hashtag exports with explicit coverage limits.
- Creator-research teams reviewing best-effort author hints at the linked posts before using them.
How you can use the data
- Review a small cats hashtag sample. Use the existing cats input with ten cards. Keep
requestedHashtag,postUrl,shortCodeand available caption text together, then open the source post before relying on the text as complete. - Compare cats and nature snapshots yourself. Use the existing two-hashtag example with a small cap per hashtag. A post can appear under both, so preserve its hashtag provenance rather than assuming global post deduplication.
- Inspect visible text when context matters. Enable rawText for a bounded card sample and compare it with cleaned caption, tags and mentions. Author hints and visible numeric text are best effort rather than verified creator records or exact engagement metrics.
- Retain evidence for later review. Keep source URLs and collection times when saving your own exports. Position reflects returned card order rather than publication time or a recent/top ranking. Thumbnails may expire, and routeStatus only compares returned count with the requested cap.
Input settings
| Setting | API key | Meaning |
|---|---|---|
| Instagram hashtags | hashtags | Required non-empty list of hashtag names or hashtag URLs. |
| Maximum posts per hashtag | maxItemsPerHashtag | 1–100 cards per hashtag. The form starts at 10 and the schema default is 20. |
| Include raw visible text | includeRawText | Optional card text in rawText. Default false. |
| Proxy configuration | proxyConfiguration | Optional connection settings. See field help. |
Hashtags are normalized to lowercase letters, numbers and underscores. Repeated normalized hashtags are processed once. Supply maxItemsPerHashtag explicitly for a predictable limit: the runtime's fallback is 24 if no schema default has been applied.
Example inputs
Use the Quick start input as a small first run. Adjust the fields described above for your own data.
Output data
- Content discovery: Public post and reel links, shortcodes and card thumbnails.
- Campaign research: Visible caption text, hashtags and mentions from hashtag cards.
- Creator leads: Best-effort author usernames and profile URLs when recognizable in the card text. Check the linked post before using them.
- Snapshot comparison: Requested hashtag, source URL, result position and scrape time.
This is useful for social listening teams, agencies and researchers collecting a bounded snapshot. It does not provide private content, comments, exact post timestamps, full captions, like counts or complete profile details. Instagram determines the displayed order. There is no Top/Recent selector or custom sorting.
More output
Each dataset item represents a visible card, not a full post. The following abbreviated example shows the output shape only, not an observed Instagram record:
{"requestedHashtag": "cats","postUrl": "https://www.instagram.com/p/EXAMPLE/","mediaType": "post","authorUsername": null,"caption": null,"hashtags": [],"mentions": [],"visibleViewCount": null,"routeStatus": "partial","position": 1}
| Fields | Meaning |
|---|---|
requestedHashtag, sourceUrl | Normalized hashtag and page used for this snapshot. |
postUrl, shortCode, mediaType | Media link, shortcode and post or reel classification. |
authorUsername, authorProfileUrl | Best-effort author inferred from visible text. Nullable. |
isVerified | Whether the visible card text contains a verification label. Absence is not proof of account status. |
caption, hashtags, mentions | Cleaned card text and tags/mentions found in that text. Not necessarily the full caption. |
visibleViewCount, visibleViewCountText | Best-effort numeric/text hints from the card. A number may be inferred from other visible text. Do not treat it as an exact engagement metric. |
thumbnailUrl | Card image URL when present. May expire. |
scrapedAt, position | Collection time, not publication time. One-based position within the hashtag's returned cards. |
routeStatus | ok when the requested limit was reached. partial when fewer cards were found. Not an independent completeness or access diagnosis. |
rawText | Included only when includeRawText is enabled. |
The same post may appear under multiple requested hashtags. Export tools can flatten array fields differently. JSON preserves their structure.
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 item event charges for each public hashtag card saved. There is no separate start event in the current pricing configuration and no synthetic error or status rows billed as content.
Use a small explicit per-hashtag cap. The possible card maximum is the number of unique normalized hashtags multiplied by that cap, though Instagram can expose fewer. See current rates on the Pricing tab.
Tips for best results
- Set the per-hashtag cap explicitly. Form, schema and runtime fallback values differ when a value is not applied.
- Keep the requested hashtag with each card. The same post can occur in more than one hashtag sample.
- Open source posts before relying on author or caption hints. Card text need not expose full content or accurate profile detail.
- Keep numeric hints labeled as uncertain. Visible view-count numbers can be inferred from unrelated card text.
- Check run outcome as well as routeStatus. Reaching a requested count is not independent proof of completeness or unrestricted access.
Limits and caveats
Only anonymously visible public hashtag cards are supported. No Instagram login, cookies, private content or login-restriction bypass is provided. Public availability changes by time and location. Empty accessible pages can finish with no rows, while navigation, execution or storage failures can fail the run. Saved rows can remain if a later hashtag fails.
No exhaustive coverage, recent-first ordering or stable cross-run result set is guaranteed. Instagram determines displayed order, with no Top/Recent selector or custom sorting. Collection times are not post timestamps. Fewer cards, empty results or a partial route label do not establish privacy or deletion.
Cards do not supply full post details, comments, exact post dates, full captions, like counts or complete profiles. Author hints and verification text are not authoritative profile records. View-count hints are not exact engagement metrics, and thumbnails can expire. Missing fields stay null or empty rather than being invented.
Hashtags are normalized and repeated normalized inputs run once, while one post can appear under several hashtags. JSON preserves tag and mention arrays most directly. Any comparison, campaign report or creator qualification is a separate downstream review.
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-hashtag-scraper/runs' \-H "Authorization: Bearer $APIFY_TOKEN" \-H 'Content-Type: application/json' \--data @- <<'JSON'{"hashtags": ["cats"],"maxItemsPerHashtag": 10}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-hashtag-scraper').call({"hashtags": ["cats"],"maxItemsPerHashtag": 10});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
Python
import osfrom apify_client import ApifyClientclient = ApifyClient(os.environ['APIFY_TOKEN'])run = client.actor('fetch_cat/instagram-hashtag-scraper').call(run_input={'hashtags': ['cats'], 'maxItemsPerHashtag': 10})print(client.dataset(run['defaultDatasetId']).list_items().items)
API usage notes
The cURL request starts an asynchronous run. Wait for completion, then read its defaultDatasetId using the Apify API. The dataset can also feed existing Make, Zapier or n8n integrations. This Actor does not contain a built-in monitoring or alerting service.
MCP and AI agents
You can ask your AI assistant to collect data with Instagram Hashtag 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 Hashtag 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-hashtag-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 Hashtag Scraper by Fetch Cat, or give it the identifier fetch_cat/instagram-hashtag-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 Hashtag Scraper to collect up to 5 visible cards for cats. Keep post links, requested hashtag and available caption text without claiming full captions or newest-first order.”
- “Collect up to 3 visible cards each for cats and nature. Keep hashtag provenance and post shortcodes for my own comparison, noting when the same post appears under both.”
- “Retrieve up to 5 cats hashtag cards with raw visible text enabled. Show source links and any author hints, flagging uncertain text or numeric hints without treating them as complete profile or engagement data.”
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
Is this an Instagram hashtag API?
It provides an Apify API for visible public hashtag cards, not an official Instagram API or a complete hashtag analytics feed. Use the returned post links to verify important findings.
Can I export Instagram hashtag data to CSV?
Yes. Open the dataset after a run and choose CSV, Excel or JSON. Only fields visible or inferred from the public cards are available. JSON retains arrays such as hashtags and mentions.
Why are fields missing or results fewer than requested?
Instagram may show limited anonymous content, omit author/caption information or block access. Check the dataset and run outcome. routeStatus only compares the returned count with the requested limit. Try one known public hashtag with a small limit when reporting an unexpected result.
Does it require Instagram login or return private content?
No Instagram account, token or cookies are used. It does not access private or login-only content. Apify authentication is separate and is required for API calls.
Related Actors
- Instagram Comments Scraper — Collect visible public comments and available author or engagement fields from known post or Reel 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 Profile & Posts Scraper — Collect public profile details and available post or Reel metadata from known accounts or media URLs.
- Instagram AI Transcript Extractor — Retrieve available transcript text from known public Instagram Reel or video URLs.
- Instagram Search Scraper — Collect visible topic-linked records from public popular-topic pages, rather than comprehensive Instagram search.
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. ♥