Instagram Hashtag Scraper : Intelligence & Trend Radar 🛰️

Instagram Hashtag Scraper — Posts, Trend Radar & Intelligence

Instagram Hashtag Intelligence & Trend Radar scrapes posts or reels published under any Instagram hashtag, hashtag URL, or keyword, then layers on a free per-hashtag intelligence report and a cross-run trend delta — both computed only from the posts it actually scraped this run. Each run returns typed JSON: individual post rows (caption, hashtags, mentions, engagement, owner, media, music), one hashtagReport summary row per hashtag, and — with trend tracking on — how many of those posts are new since the previous run. Every response is structured JSON, ready to pass directly to an LLM, index into a vector store, or feed a monitoring pipeline. It runs on Apify, so there's no server to host and no browser to babysit.

---

What is Instagram Hashtag Intelligence & Trend Radar?

Instagram Hashtag Intelligence & Trend Radar is an Apify Actor that queries Instagram's internal hashtag feed for one or more hashtags, keywords, or hashtag URLs and returns every post or reel it finds, exactly like a standard hashtag scraper. What sets it apart is what happens after the scrape: for each hashtag it also emits a free hashtagReport row that aggregates co-occurring hashtags, top mentions, audio/music trends, UTC posting-hour and weekday histograms, media-type breakdown, and engagement totals — plus, if you run it again later, a Trend Radar delta showing exactly how many posts are new since the last run, which co-hashtags and creators are emerging among those new posts, and the observed new-post rate.

It requires an authenticated Instagram session — a sessionid cookie value copied from a logged-in browser — because it talks to Instagram's private /api/v1/tags/{tag}/sections/ endpoint rather than a public, unauthenticated page. No Instagram Business or Creator account, app review, or OAuth flow is required; you supply the cookie value and the Actor handles the rest, including proxy routing and retries.

Core capabilities:

• 🏷️ Multi-query scraping — pass any mix of hashtags (webscraping or #webscraping), hashtag URLs, or free-text keywords (with keywordSearch on) in a single run; each becomes its own section in the output
• 🎞️ Posts or reels — contentType switches the feed tab between photo/video/carousel posts and short-form reels
• 🧠 Free intelligence report — one hashtagReport row per hashtag with co-occurring hashtags, top mentions, audio trends, posting-time histograms, media-type breakdown, engagement stats, and top creators/posts — all derived from the posts actually scraped
• 📈 Trend Radar — post IDs are persisted per hashtag in a named key-value store between runs, so every subsequent run reports a real new-vs-seen delta instead of a fresh, disconnected snapshot
• 🛡️ Resilient by default — a proxy ladder (your proxy choice → Apify RESIDENTIAL → direct) with a sticky per-run IP, exponential-backoff retries, and Chrome-fingerprinted HTTP requests via impit
• 🔢 Configurable depth and ranking size — resultsLimit controls posts collected per hashtag, topN controls how many entries appear in each ranked list inside the report

---

What data can you get with Instagram Hashtag Intelligence & Trend Radar?

The Actor writes three distinct kinds of dataset row — section headers, post rows, and hashtag report rows — distinguished by the isSection / isReport flags.

Result Type	Extracted Fields	Primary Use Case
Section header (free)	section, isSection, label, sectionPosition, rawQuery, contentType, inputUrl	Marks where each hashtag's block of results starts in the dataset
Post row (billed)	id, type, shortCode, caption, hashtags, mentions, url, commentsCount, firstComment, latestComments, dimensionsHeight, dimensionsWidth, displayUrl, images, likesCount, videoPlayCount, videoViewCount, timestamp, childPosts, ownerFullName, ownerUsername, ownerId, productType, videoUrl, videoDuration, musicInfo	Raw post-level dataset for content research, UGC discovery, and feed rebuilding
Hashtag report (free)	reportHashtag, contentType, scrapedAt, postsAnalyzed, likesKnownFor, totalLikes, avgLikes, medianLikes, totalComments, avgComments, medianComments, mediaTypeBreakdown, coHashtags, topMentions, audioTrends, postingHoursUtc, postingWeekdaysUtc, topCreators, topPosts, trendIsFirstRun, trendNewCount, trendNewSincePrevRunAt, trendTotalKnownIds, trendEmergingCoHashtags, trendRisingCreators, trendObservedNewPerHour	Per-hashtag performance snapshot and cross-run monitoring without building a spreadsheet by hand

🛰️ Trend Radar & Intelligence Report

This is the section competing hashtag scrapers don't have. After each hashtag finishes scraping, the Actor pushes one free hashtagReport row built entirely from that hashtag's own scraped posts — no external datasets, no modeled scores, no constant lookup tables. coHashtags counts which other hashtags actually co-occur in the scraped captions; audioTrends parses each post's real musicInfo object (handling both the music_asset_info and original_sound_info shapes Instagram returns) to surface which tracks recur; postingHoursUtc and postingWeekdaysUtc are literal histograms of each post's own timestamp. If trackTrends is on, the Actor also persists the set of post IDs seen for that hashtag in a named key-value store, so the next run can report trendNewCount (posts not seen before), trendEmergingCoHashtags and trendRisingCreators (computed only from the new posts), and trendObservedNewPerHour (new posts ÷ hours since the previous run). A minimal row looks like:

{
  "type": "hashtagReport",
  "isReport": true,
  "reportHashtag": "webscraping",
  "postsAnalyzed": 20,
  "likesKnownFor": "17/20",
  "avgLikes": 341.2,
  "medianLikes": 210,
  "coHashtags": [{ "tag": "python", "count": 6 }],
  "audioTrends": [{ "title": "Original audio", "artist": "user123", "audioId": "9911", "uses": 3 }],
  "trendIsFirstRun": false,
  "trendNewCount": 4,
  "trendObservedNewPerHour": 0.083
}

📸 Post rows

Post rows are pushed byte-for-byte identical to what a plain hashtag scraper returns, so anything built to consume a standard Instagram post dataset works unmodified here. Each row carries the post's id, shortCode and public url, its caption with hashtags/mentions already parsed out, engagement (likesCount, commentsCount, videoPlayCount/videoViewCount for video), the owner (ownerUsername, ownerFullName, ownerId), and media metadata including childPosts for carousels. When Instagram hides a post's like count, likesCount is written as -1 rather than a fabricated 0 — the intelligence layer treats -1 as unknown and excludes it from totalLikes/avgLikes/medianLikes, which is what likesKnownFor (e.g. "17/20") reports.

---

How does Instagram Hashtag Intelligence & Trend Radar differ from the official Instagram API?

Meta's Instagram Platform API does expose a hashtag lookup — the Hashtag Search endpoint (GET /ig_hashtag_search plus {hashtag-id}/top_media and {hashtag-id}/recent_media) — but it is built for Business and Creator accounts auditing their own audience, not for open-ended hashtag research, and it is gated well below what this Actor allows.

Feature	Instagram Hashtag Search API	Instagram Hashtag Intelligence & Trend Radar
Access requirement	Approved Business or Creator account, app review, and the Instagram Public Content Access feature	An Instagram sessionid cookie value; no app review
Hashtags per period	Capped at 30 unique hashtags in a rolling 7-day period (per Meta's Instagram Platform documentation)	No Actor-side cap on distinct hashtags; bounded only by resultsLimit and your run's charge limit
Query type	Exact hashtag name only, via ig_hashtag_search	Hashtag, hashtag URL, or free-text keyword auto-resolved to a hashtag (keywordSearch)
Result feed	top_media or recent_media for the queried hashtag	posts or reels, selectable per run via contentType
Aggregation	None — raw media list only	Free per-hashtag hashtagReport (co-hashtags, mentions, audio, posting-time histograms, engagement stats) generated automatically
Cross-run trend delta	Not provided — every call is stateless	trackTrends persists seen post IDs and reports what's new since the previous run
Setup time	OAuth app, Business/Creator account conversion, Meta App Review	Copy one cookie value from a logged-in browser

The official API is the right tool when you already run a Business or Creator account, only need hashtags you own or are reviewed for, and want data inside Meta's own infrastructure. Instagram Hashtag Intelligence & Trend Radar is the right tool for ad-hoc or competitor hashtag research, monitoring hashtags you don't own, or any case where the 30-hashtag/7-day ceiling and app review process aren't workable.

---

What is the difference between a hashtag scraper and a hashtag trend monitor?

A hashtag scraper returns a snapshot: run it once and you get the posts under a hashtag right now. A hashtag trend monitor is the same underlying scrape run repeatedly, with state kept between runs so it can tell you what changed — which posts are new, which co-hashtags are rising, which creators just started posting into the tag. The distinction matters because a snapshot answers "what does this hashtag look like today," while a monitor answers "what changed on this hashtag since I last checked" — the question campaign trackers, UGC teams, and trend researchers actually need answered on a recurring basis.

Instagram Hashtag Intelligence & Trend Radar does both from one Actor and one input schema. Every run scrapes fresh posts and pushes them as ordinary dataset rows (the scraper half). When trackTrends is on, the same run also diffs the scraped post IDs against a persisted per-hashtag ID set and writes a hashtagReport row carrying trendNewCount, trendEmergingCoHashtags, trendRisingCreators, and trendObservedNewPerHour (the monitor half). There's no separate "monitoring mode" Actor to switch to — turning trackTrends off falls back to scraper-only behavior, and turning it on (the default) adds the delta on top without changing what the post rows themselves contain.

---

How to scrape Instagram with Instagram Hashtag Intelligence & Trend Radar?

1. Open Instagram Hashtag Intelligence & Trend Radar on its Apify Store listing and click Try for free (or Run, if you've already added it to your account).
2. Enter one or more hashtags, hashtag URLs, or keywords in startUrls — for example webscraping, #webscraping, https://www.instagram.com/explore/tags/webscraping/, or a plain keyword with keywordSearch turned on.
3. Paste your Instagram sessionid cookie value into the sessionid field (required), then set contentType (posts or reels), resultsLimit, and optionally proxyConfiguration if you want a specific Apify Proxy group.
4. Click Start and watch the run log — the Actor streams a section header, then post rows, then a free hashtagReport row for each hashtag in startUrls, in order.
5. Download the results from the Dataset tab as JSON, CSV, Excel, XML, or RSS, or pull them programmatically via the Apify API / apify-client.

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")

run = client.actor("instagram-hashtag-intelligence-radar").call(run_input={
    "startUrls": ["webscraping", "#datascraping"],
    "sessionid": "<YOUR_INSTAGRAM_SESSIONID>",
    "contentType": "posts",
    "resultsLimit": 50,
    "emitIntelligence": True,
    "trackTrends": True,
})

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

How to run multiple queries in one job

startUrls accepts an array, so a single run can cover any mix of hashtags, hashtag URLs, and keywords — each entry becomes its own labeled section in the dataset (sectionPosition reports its position, e.g. "2/5") with its own hashtagReport row. There's no separate batch-upload format or documented per-hashtag concurrency setting in the schema; queries are processed one after another within the run, and a run stops early only if it hits the configured ACTOR_MAX_TOTAL_CHARGE_USD charge limit or an Instagram session failure.

---

⬇️ Input

All ten input fields live in one schema. startUrls and sessionid are required; everything else has a default. intelligenceOptions is a schema-level section divider (its editor is hidden) that groups emitIntelligence and trackTrends in the Input UI — it isn't a control you set directly.

Parameter	Required	Type	Description	Example Value
startUrls	Yes	array	Hashtags, hashtag URLs, or keywords (with keywordSearch on). Each item becomes its own section + intelligence report.	["webscraping", "#datascraping"]
sessionid	Yes	string (secret)	Instagram sessionid cookie value, from DevTools → Application → Cookies → instagram.com.	"58012345678%3Aabcdefgh..."
contentType	No	string (posts | reels)	Feed tab to scrape — photo/video/carousel posts, or short-form reels. Default "posts".	"reels"
keywordSearch	No	boolean	ON auto-resolves a keyword to its matching hashtag; OFF treats the input as a literal hashtag. Default false.	true
resultsLimit	No	integer (1–1000)	Posts to collect per hashtag. Default 20.	100
intelligenceOptions	No	boolean	Hidden section-caption toggle grouping the two options below; not a user-facing control. Default true.	—
emitIntelligence	No	boolean	Adds one free hashtagReport summary row per hashtag with co-hashtags, mentions, audio trends, posting-time histograms, media-type breakdown, and engagement stats. Default true.	true
trackTrends	No	boolean	Persists seen post IDs per hashtag between runs and reports how many are new since the previous run, plus emerging co-hashtags/creators. Default true.	true
topN	No	integer (1–50)	How many entries to keep in each ranked list inside the report (co-hashtags, mentions, audio, creators, top posts). Default 10.	15
proxyConfiguration	No	object	Apify Proxy configuration. Default { "useApifyProxy": false } — the Actor still applies a RESIDENTIAL-then-direct fallback ladder internally even when this is off.	{ "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }

Example JSON input

{
  "startUrls": ["webscraping", "#photography"],
  "sessionid": "58012345678%3Aabcdefghijklmnop%3A1%3A...",
  "contentType": "posts",
  "keywordSearch": false,
  "resultsLimit": 50,
  "emitIntelligence": true,
  "trackTrends": true,
  "topN": 10,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

Common pitfall: with keywordSearch left at its default false, a plain phrase in startUrls is treated as a literal hashtag, not searched — "web scraping tips" will be queried as the (almost certainly empty) hashtag webscrapingtips rather than resolved to a real one. Turn keywordSearch on for free-text keywords, and leave it off when you're already passing an exact hashtag. A second, more common failure mode: an expired or flagged sessionid produces a single free diagnostic row (isDiagnostic: true, ok: false) explaining the cause instead of any post rows — refreshing the cookie value resolves it.

---

⬆️ Output

Every row is typed, normalized JSON with a consistent schema across runs — section headers, billed post rows, and free hashtagReport rows all land in the same dataset, distinguished by isSection / isReport. Like every Apify dataset, results can be exported as JSON, CSV, Excel, XML, or RSS from the Dataset tab, or streamed via the Apify API. Two dataset views are published: Scraped Posts — Section View (the default, 33 fields covering section headers and post rows) and Hashtag Intelligence & Trend (the 26 report-level fields above).

Scraped results

[
  {
    "section": "webscraping",
    "isSection": true,
    "rawQuery": "webscraping",
    "contentType": "posts",
    "sectionPosition": "1/1",
    "inputUrl": "https://www.instagram.com/explore/tags/webscraping",
    "label": "=== Section 1/1: #webscraping (posts) ==="
  },
  {
    "inputUrl": "https://www.instagram.com/explore/tags/webscraping",
    "id": "3401234567890123456",
    "type": "Image",
    "shortCode": "C9xY2AbCdEf",
    "caption": "Scraping tips for beginners #webscraping #python #data",
    "hashtags": ["webscraping", "python", "data"],
    "mentions": [],
    "url": "https://www.instagram.com/p/C9xY2AbCdEf/",
    "commentsCount": 14,
    "firstComment": "Great breakdown!",
    "latestComments": ["Great breakdown!", "Saving this"],
    "dimensionsHeight": 1350,
    "dimensionsWidth": 1080,
    "displayUrl": "https://scontent.cdninstagram.com/...jpg",
    "images": ["https://scontent.cdninstagram.com/...jpg"],
    "likesCount": 482,
    "timestamp": "2026-07-20T14:03:11.000Z",
    "childPosts": [],
    "ownerFullName": "Jane Data",
    "ownerUsername": "jane.scrapes",
    "ownerId": "9988776655",
    "productType": "feed",
    "musicInfo": null,
    "section": "webscraping"
  },
  {
    "inputUrl": "https://www.instagram.com/explore/tags/webscraping",
    "id": "3401234567890123457",
    "type": "Reel",
    "shortCode": "C9xY2XyZaB1",
    "caption": "5 web scraping mistakes to avoid #webscraping #coding",
    "hashtags": ["webscraping", "coding"],
    "mentions": ["datateamhq"],
    "url": "https://www.instagram.com/reel/C9xY2XyZaB1/",
    "commentsCount": 31,
    "firstComment": "",
    "latestComments": [],
    "dimensionsHeight": 1920,
    "dimensionsWidth": 1080,
    "displayUrl": "https://scontent.cdninstagram.com/...jpg",
    "images": ["https://scontent.cdninstagram.com/...jpg"],
    "likesCount": -1,
    "videoPlayCount": 15234,
    "videoViewCount": 22110,
    "timestamp": "2026-07-21T09:41:52.000Z",
    "childPosts": [],
    "ownerFullName": "Dev Notes",
    "ownerUsername": "dev.notes.daily",
    "ownerId": "1122334455",
    "productType": "clips",
    "videoUrl": "https://scontent.cdninstagram.com/...mp4",
    "videoDuration": 27.5,
    "musicInfo": { "music_asset_info": { "title": "Original audio", "display_artist": "dev.notes.daily", "audio_id": "778899" } },
    "section": "webscraping"
  },
  {
    "type": "hashtagReport",
    "isReport": true,
    "section": "webscraping",
    "reportHashtag": "webscraping",
    "rawQuery": "webscraping",
    "contentType": "posts",
    "scrapedAt": "2026-07-26T10:15:02.118Z",
    "postsAnalyzed": 20,
    "likesKnownFor": "17/20",
    "totalLikes": 5801,
    "avgLikes": 341.2,
    "medianLikes": 210,
    "totalComments": 612,
    "avgComments": 30.6,
    "medianComments": 18,
    "mediaTypeBreakdown": { "Image": 9, "Reel": 8, "Sidecar": 3 },
    "coHashtags": [{ "tag": "python", "count": 6 }, { "tag": "data", "count": 5 }],
    "topMentions": [{ "username": "datateamhq", "count": 2 }],
    "audioTrends": [{ "title": "Original audio", "artist": "dev.notes.daily", "audioId": "778899", "uses": 3 }],
    "postingHoursUtc": { "9": 2, "14": 5, "20": 3 },
    "postingWeekdaysUtc": { "Monday": 4, "Wednesday": 6 },
    "topCreators": [{ "username": "jane.scrapes", "posts": 2, "totalLikes": 890, "totalComments": 22 }],
    "topPosts": [{ "url": "https://www.instagram.com/p/C9xY2AbCdEf/", "ownerUsername": "jane.scrapes", "likesCount": 482, "commentsCount": 14, "timestamp": "2026-07-20T14:03:11.000Z" }],
    "trendIsFirstRun": false,
    "trendNewCount": 4,
    "trendNewSincePrevRunAt": "2026-07-19T08:00:00.000Z",
    "trendTotalKnownIds": 87,
    "trendEmergingCoHashtags": [{ "tag": "python", "count": 2 }],
    "trendRisingCreators": [{ "username": "dev.notes.daily", "newPosts": 2 }],
    "trendObservedNewPerHour": 0.083
  }
]

---

How can I use the data extracted with Instagram Hashtag Intelligence & Trend Radar?

• 📣 Social and marketing teams: track a branded or campaign hashtag's real post volume, top-performing content, and which creators are organically posting into it, using the topCreators and topPosts fields without building a tracking spreadsheet.
• 🤖 AI engineers and LLM developers: a grounded agent architecture — an agent issues a hashtag query, receives structured JSON post and report rows back, and passes it to the model as up-to-date context instead of relying on the model's training data.
• 📊 Market and trend researchers: compare hashtagReport rows across a set of related hashtags to gauge relative activity, co-hashtag overlap, and posting-time patterns without manually tallying raw post lists.
• 🎧 Content and creator teams: use audioTrends and mediaTypeBreakdown to spot which sounds and formats are recurring under a hashtag before briefing a creative team.

---

How do you monitor Trend Radar over time?

Trend monitoring here means running the same hashtag query repeatedly and comparing the hashtagReport row each run produces, rather than treating every scrape as an isolated snapshot. Because trackTrends persists each hashtag's seen post IDs in a named key-value store (instagram-hashtag-trend-state) that survives between runs, every run after the first can tell you exactly what changed: trendNewCount is how many scraped posts weren't seen in any prior run, trendEmergingCoHashtags and trendRisingCreators are computed only from those new posts (so a hashtag suddenly picked up by a new cluster of accounts shows up here before it shows up in the raw totals), and trendObservedNewPerHour gives the new-post rate observed between this run and the last one you actually ran.

The fields worth diffing run-to-run are trendNewCount, trendEmergingCoHashtags, trendRisingCreators, totalLikes/avgLikes (to catch an engagement shift, not just a volume shift), and mediaTypeBreakdown (to catch a format shift, e.g. a hashtag moving from posts to reels). A practical loop: schedule the Actor to run daily or hourly across your hashtag set using Apify's built-in Scheduler, pull each run's hashtagReport rows via the Apify API, and alert your team when trendNewCount or trendObservedNewPerHour spikes past what you'd normally expect for that hashtag. Deleting the named key-value store resets a hashtag's history and makes the next run report as a first run again.

---

Integrate Instagram Hashtag Intelligence & Trend Radar and automate your workflow

Instagram Hashtag Intelligence & Trend Radar works with any language or tool that can send an HTTP request — it's an Apify Actor, reachable through the Apify API and every official Apify client library.

REST API with Python

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")

run = client.actor("instagram-hashtag-intelligence-radar").call(run_input={
    "startUrls": ["webscraping"],
    "sessionid": "<YOUR_INSTAGRAM_SESSIONID>",
    "resultsLimit": 100,
})

reports = [
    item for item in client.dataset(run["defaultDatasetId"]).iterate_items()
    if item.get("isReport")
]
print(reports)

Swap apify_client for a plain HTTPS POST to https://api.apify.com/v2/acts/instagram-hashtag-intelligence-radar/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN> if you'd rather not add a dependency — the response is the finished dataset as a JSON array.

Scheduled monitoring and delivery

Set up a recurring run from the Actor's Schedule tab in Apify Console (any cron expression), which is what makes the trackTrends delta meaningful run over run. There's no actor-specific webhook payload documented in this Actor's code, but Apify's platform-level run webhooks (Console → Integrations → Webhooks) can notify an endpoint of your choosing whenever a scheduled run finishes, and the dataset itself is always pollable via the API in the meantime.

---

Is it legal to scrape Instagram results?

Scraping publicly accessible data is generally lawful in the United States — courts have held that accessing data any visitor can see without logging in or bypassing an access control does not violate the Computer Fraud and Abuse Act (hiQ Labs, Inc. v. LinkedIn Corp., 9th Cir. 2019). Instagram Hashtag Intelligence & Trend Radar returns only what a logged-in viewer of a public hashtag page can already see — it doesn't access private accounts or bypass any access restriction beyond authenticating as the account whose sessionid you supply. Because captions, usernames, and mentions are personal data, storing or reusing scraped output at scale can still fall under GDPR or CCPA depending on your jurisdiction and use case, and Instagram's own Terms of Use separately restrict automated access regardless of what the law permits. Scraping for one-off research and scraping for AI training or bulk commercial storage carry different risk profiles. Consult your legal team for commercial use cases involving bulk data storage.

---

❓ Frequently asked questions

Can I search by keyword instead of an exact hashtag?

Yes — set keywordSearch to true and put a free-text term in startUrls. The Actor calls Instagram's own hashtag search (web/search/topsearch/) to resolve your keyword to its best-matching hashtag before scraping. With keywordSearch off (the default), the same entry is treated as a literal hashtag name.

How do I control how many posts come back?

resultsLimit sets posts collected per hashtag, from 1 to 1000 (default 20). contentType further filters the feed to posts (Image/Video/Sidecar) or reels (Reel only) before the limit is applied. Pagination for a hashtag also stops early if Instagram reports no further pages or returns three consecutive empty pages.

How does Instagram Hashtag Intelligence & Trend Radar handle Instagram's anti-bot measures?

Requests are made through impit, which reproduces a real Chrome TLS/HTTP fingerprint rather than a generic HTTP client, and route through a proxy ladder that tries your chosen proxy first, then Apify's RESIDENTIAL group, then a direct connection — with a sticky IP held for the whole run rather than rotated per request, since Instagram treats mid-session IP hopping as suspicious. Retryable failures (HTTP 429/500/502/503/504/403) back off with jitter and, on repeated 403s, drop to the next proxy tier. A genuine checkpoint_required or login_required response from Instagram is treated as an authentication failure, not a retryable one, and stops the run for that session.

Does Instagram Hashtag Intelligence & Trend Radar extract trend and intelligence data?

Yes. With emitIntelligence on (default), each hashtag gets a free hashtagReport row with coHashtags, topMentions, audioTrends, postingHoursUtc/postingWeekdaysUtc, mediaTypeBreakdown, engagement totals, and topCreators/topPosts. With trackTrends also on (default), the same row adds trendNewCount, trendEmergingCoHashtags, trendRisingCreators, and trendObservedNewPerHour. The report row is only pushed when at least one post was collected for that hashtag; a hashtag that returns zero posts gets no report row.

How many results does Instagram Hashtag Intelligence & Trend Radar return per query?

Up to resultsLimit posts per hashtag (1–1000, default 20), subject to however many posts Instagram's hashtag feed actually has to serve and your run's configured charge limit. There is no separate Actor-imposed cap beyond resultsLimit itself.

How do I monitor a hashtag's activity over time?

Turn trackTrends on and re-run the same hashtag on a schedule (Apify's Schedule tab, or your own cron trigger via the API). Each subsequent run's hashtagReport row reports trendNewCount and the other trend fields relative to the previous run, because seen post IDs persist between runs in a named key-value store — you don't need to diff datasets yourself.

Does Instagram Hashtag Intelligence & Trend Radar work with Claude, ChatGPT, and AI agent frameworks?

It's callable as an HTTP endpoint through the Apify API by any agent framework capable of making a request — an agent can trigger a run, poll or await the dataset, and pass the resulting JSON to the model as grounded, current context. No dedicated MCP server is documented for this Actor.

How does Instagram Hashtag Intelligence & Trend Radar compare to other Instagram hashtag scrapers?

As observed on the Apify Store on 2026-07-26, instaprism/instagram-hashtag-monitor markets itself as requiring no Instagram login and includes webhook alerting and a per-hashtag summary (newPostsCount, avgLikes, avgComments, topPost) — but its documented summary has no co-hashtag list, no audio/music trend detection, no posting-time histograms, no media-type breakdown, and no emerging-co-hashtag or rising-creator fields. This Actor requires an Instagram sessionid (a real tradeoff — you're borrowing your own session rather than the provider's shared infrastructure) but returns a materially deeper per-hashtag report for that cost, and — like instagram-hashtag-monitor — charges per event rather than a flat monthly fee. Per the Apify Store's own listing snapshot from 2026-07-08, the base Actor in this family, scrapier/instagram-hashtag-scraper, ships the identical scraping core under a flat monthly price with no intelligence or trend layer at all; this Actor adds both on top for the same post-row output.

Can I use Instagram Hashtag Intelligence & Trend Radar without managing proxies or my own infrastructure?

Yes for infrastructure — the Actor runs on Apify's servers, and its internal proxy ladder (your proxyConfiguration choice, then Apify RESIDENTIAL, then direct) handles routing and retries automatically even if you leave proxyConfiguration at its default. What you must supply yourself is a valid, currently-logged-in Instagram sessionid cookie — the Actor cannot generate or refresh that on your behalf.

---

💬 Your feedback

Found a bug or missing a field? We want to know. Report it on the Actor's Issues tab in Apify Console, or reach out through your Apify account's support channel — active maintenance is how this Actor keeps working against Instagram's current endpoints.