Instagram scraper API

Yes. Social Fetch's Instagram routes read public profile, post, Reel, highlight, and search data over REST. You authenticate with a Social Fetch API key only — no Meta App Review, no linked Business or Creator account, no Facebook Page, and no OAuth consent screen for the account you're looking up.

Profiles by handle or numeric user id, an engagement audit of a profile's recent posts, profile posts, Reels and tagged posts (separate cursor-paginated lists), live stories, saved highlight albums and the story items inside one, the accounts a profile follows, where an account is based and when it joined, single posts and Reels by URL with comments, replies, transcripts and media downloads, hashtags and locations with their live post feeds, Reels that reuse an audio id, and search (accounts, hashtags, profiles, Reels, Popular topics, audio) plus a trending-Reels sample. Exact paths, params, and response fields are on this hub's endpoint list and under /docs/api.

Use GET /v2/instagram/profiles/{profile}: it takes a username (with or without the leading @), a profile URL or a numeric user id, and uses found, private or not_found on data.lookupStatus (restricted is rare). Add include=recentMedia for the latest grid posts and include=about for where the account is based and when it joined.

GET /v2/instagram/profiles/{profile}/media pages one tab of a profile at a time: tab=posts is the mixed public grid (images, carousels and in-feed video), tab=reels the Reels tab with play counts, and tab=tagged the posts other accounts tagged it in. Every item is the shared v2 media object, and each tab paginates with its own cursor/nextCursor.

GET /v2/instagram/profiles/{profile}/media?tab=tagged pages the public Tagged tab by handle, profile URL or user id; each item is the shared v2 media object.

Yes, both. GET /v2/instagram/profiles/{profile}/stories lists a public profile's live stories from the last 24 hours, oldest first, in one response (an empty array when none are live), by handle, profile URL or user id. GET /v2/instagram/profiles/{profile}/highlights and GET /v2/instagram/highlights/{highlightId} list a profile's saved highlight albums (title, cover thumbnail) and open one album into its stories, with each story as the shared media object. Story items carry media URLs, timestamps, mentions, and link stickers when present.

Yes. GET /v2/instagram/profiles/{profile}/following lists the accounts a public profile follows, in the order Instagram lists them. Each account is the shared v2 profile summary: id, handle, displayName, avatarUrl, verified and privateAccount. Keep passing data.page.nextCursor while data.page.hasMore is true to reach the end of the list. A private profile returns lookupStatus: private with no accounts. Follower lists aren't offered: Instagram only shows a small sample of an account's followers.

Yes. GET /v2/instagram/media/{media}/comments takes a shortcode, URL or media id and returns top-level comments — text, author handle, like count, reply count — in Instagram's ranked order (sort=top, the default) or sort=newest, paginated with an opaque cursor while data.page.hasMore is true. Replies below a top-level comment are GET /v2/instagram/media/{media}/comments/{commentId}/replies.

Call GET /v2/instagram/media/{media}/transcript with a shortcode, a /p/, /reel/ or /tv/ URL, or a media id — there is no separate Reel-only transcript path. It returns one transcript with text and durationSec; a video with no speech is found with a null text.

GET /v2/instagram/hashtags/search finds hashtags by keyword (one ranked set with post counts, no cursor); pass a name to GET /v2/instagram/hashtags/{hashtag} or its /media for the tag's posts. GET /v2/instagram/profiles/search finds accounts by keyword, cursor-paginated. GET /v2/instagram/reels/search runs a keyword search scoped to Reels and pages with a cursor (data.page.nextCursor). GET /v2/instagram/locations/search finds places by name and returns each place's location id, name and coordinates (one set, no cursor); pass an id to GET /v2/instagram/locations/{locationId} or its /media. GET /v2/instagram/reels/trending takes no query params and returns one fresh sample batch of Reels as shared v2 media objects (call it again for another), and GET /v2/instagram/topics/{topic} is the Popular topic page in v2 (the topic's details on the first page, then its curated posts as media, cursor-paginated). GET /v2/instagram/audio/search finds songs and original sounds by keyword (one ranked set, no cursor) and returns each result's id. Pass an audio id (from search, a Reel's audio.id, or the numeric id in an instagram.com/reels/audio/{audioId}/ URL) to GET /v2/instagram/audio/{audioId} for the audio's details (an id from search can occasionally resolve to not_found; then try that result's assetId), or to GET /v2/instagram/audio/{audioId}/media to page the Reels that use it.

Almost every Instagram operation is a flat 1 credit per completed lookup, including each page of a paginated list (a list that ends on an empty page still bills that page). The exceptions are GET /v2/instagram/media/{media}?include=files, which adds a 10-credit surcharge (11 total) when the files are hosted, GET /v2/instagram/profiles/{profile}, where include=recentMedia and include=about add 1 credit each when served, and the engagement audit, which is 5 credits for an audited profile (on the v2 route, 1 credit for a private or missing one). Signup includes 100 free credits and pay-as-you-go packs don't expire. Confirm every call with meta.creditsCharged.

Every profile route (profile, basic, engagement, posts, reels, highlights, stories, tagged posts) uses the same data.lookupStatus values: private for private accounts and not_found for unknown ones (stories have no restricted). Age-gated accounts return found with their public data; restricted is rare and means Instagram withholds the account from public view. The v2 profile's include=about is served for private accounts too, because Instagram shows that panel for them. Post detail uses restricted only for posts Instagram withholds from public view. None of these routes invent placeholder data for content that isn't public. Social Fetch only returns publicly visible Instagram data; you're responsible for using it in line with Instagram's terms and applicable law, and we don't provide legal advice.