Instagram Post Scraper With Tagged Accounts

Instagram post scraper that expands who appears on each post: in-photo tagged accounts, official collab coauthors, and caption @mentions. Full post export (caption, likes, comments, media, timestamp) stays in place. Filter by collabs or a handle allow-list.

This is an Instagram data extractor / Instagram post scraper / Instagram tagged users scraper for profiles, post URLs, reel URLs and tv URLs. No login cookie is required for photo tags, collabs or caption mentions.

---

What this actor does

• Instagram profile or post URL input — handles, profile URLs, /p/, /reel/, /tv/.
• Photo-tagged accounts from usertags (username, id, verified, private, profile URL, tag X/Y when Instagram sends a position).
• Official collab partners from coauthor_producers.
• Caption @mentions parsed separately (not mixed into photo tags; emails are not mined as handles).
• Union list peopleOnPost with source = photoTag | coauthor | captionMention.
• Filters — all posts (default), photo-tagged only, collabs only, caption-mention only, optional handle allow-list, scan ceiling.
• Optional people table ig-people-<runId> — one uncharged child row per person (type, isChild, parentId).
• Instagram post export fields — caption, hashtags, mentions, likes, comments, image renditions, video URL, carousel children.

---

Input example

{
  "username": ["https://www.instagram.com/nike/"],
  "resultsLimit": 12,
  "dataDetailLevel": "basicData",
  "peopleFilter": "all",
  "taggedUsernames": [],
  "emitPeopleDataset": true
}

A base-shaped payload still works:

{
  "username": ["nike"],
  "resultsLimit": 5,
  "skipPinnedPosts": false,
  "dataDetailLevel": "detailedData"
}

Input fields

Field	Type	Default	What it does
username	array (required)	nike profile URL	Usernames, profile URLs, post / reel / tv URLs
resultsLimit	integer	10	Posts saved per profile
onlyPostsNewerThan	date	empty	Absolute or relative cutoff
skipPinnedPosts	boolean	false	Drop pins on this profile's grid
dataDetailLevel	enum	detailedData	Extra post-page fields vs feed-only
peopleFilter	enum	all	all / photoTagged / collabs / captionMention
taggedUsernames	array	[]	Keep posts that include these handles as tag, coauthor or caption mention
maxPostsToScan	integer	300	Scan budget when a people filter or allow-list is on
emitPeopleDataset	boolean	true	Extra uncharged people table
proxyConfiguration	proxy	Apify RESIDENTIAL	Declared input (was hidden on the original)

---

Output fields

Always on the post row (empty list / 0 / false when nobody is tagged):

Field	Meaning
taggedUsers	Photo tags with identity + tagX/tagY when present
coauthorProducers	Official collab partners
captionMentions	Handles parsed from the caption
taggedUserCount / coauthorCount / captionMentionCount / peopleOnPostCount	Counts
isCollab	True when coauthorCount > 0
peopleOnPost	Deduped union with a source label

Base post fields remain: id, type, shortCode, caption, hashtags, mentions, url, commentsCount, likesCount, timestamp, displayUrl, images, childPosts, ownerUsername, ownerFullName, ownerId, isCommentsDisabled, plus detailed/video keys when those modes apply.

Child people rows (optional dataset): type (taggedUser / coauthor / captionMention), isChild, parentId, parentUrl, username, profileUrl, tagX, tagY.

Coverage is creator-dependent. Fashion and brand collab accounts are dense; a news account can have almost no photo tags. Default peopleFilter=all so that does not empty the dataset.

---

Use cases

• Instagram tagged users export for UGC and rights tracking
• Instagram collab / coauthor audit for a brand profile
• Instagram caption mention scrape for campaign handles
• Instagram post scraper with a people table for spreadsheets
• Filter an Instagram profile scrape down to posts that tag a partner

---

Notes

• Photo tags, collabs and caption mentions come from the profile feed. No Instagram session cookie.
• peopleFilter other than all can legitimately return zero rows on low-tag accounts — raise maxPostsToScan or leave the filter on all.
• images[] is filled from Instagram's own rendition list. Comments on detailed runs use the live comments_connection container.
• Monetization event id is row_result (one charge per saved post). People-table rows are not charged.