Profiles, user posts, post details, and media URLs each have one fixed-purpose Actor. Pick the record you need, then run it from the web, API, schedule, or integration.
Use Profile for account metadata, User Posts for a public feed, Post Details for known shortcodes, and Media URL Extractor for image or video URLs. Web results can be copied, downloaded, and exported as CSV or JSON; every Actor also writes batch results to an Apify Dataset.
Processes publicly accessible Instagram content onlyTOK//LAB is not affiliated with Instagram or MetaMaintained by spider_studio
Interface directory
One result type per Actor
Separate contracts make retry scope and downstream schemas predictable—and prevent one request from silently collecting unrelated data.
01
ACCOUNT METADATA
Instagram Public Profile Scraper API
spider_studio/instagram-profile
Submit public usernames in bulk and collect names, bios, profile images, audience counts, verification flags, and related accounts.
Choose a profile, feed, post-detail, or media resolver based on the public identifier you already have.
02NORMALIZE
Keep one object per Dataset row
Profile, post, and media URL records stay separate for clean tables, retries, and automation.
03DELIVER
Export, schedule, or integrate
Use the Apify API, webhooks, schedules, and Dataset exports in JSON, CSV, Excel, and other formats.
Operator notes
Decide which object you actually need to store
Profiles and posts have different grain
Profile writes one row per username. User Posts writes one row per discovered post, so output volume and downstream uses differ.
A URL is a reference, not a permanent file
Media CDN URLs can expire. Retain the shortcode, collection time, and asset metadata, then resolve again when needed.
Start with small batches and defaults
Test a few public inputs and confirm the output before raising pages or concurrency.
Normalized output
How the four interfaces divide the work
usernames[]
Profile returns account metadata; User Posts returns public posts published by those accounts.
postCodes[]
Post Details resolves known shortcodes from /p/ or /reel/ URLs in bulk.
postIdsOrUrls[]
Media URL Extractor accepts shortcodes and official Instagram HTTPS share links.
assets[]
Post and media interfaces describe images, videos, dimensions, and position in an ordered array.
success / error
Per-input status and diagnostics keep failed work distinct from valid empty values.
Common questions
Instagram API selection FAQ
Do these Actors require an Instagram login?
No. These four Actors are designed for public content without Instagram usernames, passwords, or session cookies. Private, deleted, region-restricted, or login-gated content may not resolve.
How do User Posts and Post Details differ?
User Posts discovers paginated content from usernames. Post Details accepts shortcodes you already know and resolves a normalized record for each one.
Does Media URL Extractor store images or videos?
It does not host files on the server. It returns current CDN URLs and metadata; the web page can ask your browser to download a public asset, but those URLs can expire.
Can I run these through an API or schedule?
Yes. Each Actor supports Apify Console runs, REST and client APIs, webhooks, schedules, and common integrations.