账号资料数据增强
Use Instagram endpoints to turn 账号资料数据增强 into repeatable API requests with documented inputs and JSON responses.
将 Instagram 的公开数据转化为结构化输入，用于社交聆听和创作者研究。
通过文档化的网络数据抓取 API 端点获取 Instagram 的账号资料、帖子和搜索信号。
Endpoint families
4
Documented params
14
Examples
5
Live catalog snapshot
Active endpoints
5
Methods
GET
Required params
11
Schema refs
5
{
"platform": "Instagram",
"endpoint": "instagram-post",
"method": "GET",
"path": "/instagram/post/{id}/{post_id}",
"auth": "apiKey"
}Use cases
通过文档化的网络数据抓取 API 端点获取 Instagram 的账号资料、帖子和搜索信号。
Use Instagram endpoints to turn 账号资料数据增强 into repeatable API requests with documented inputs and JSON responses.
Use Instagram endpoints to turn 帖子元数据采集 into repeatable API requests with documented inputs and JSON responses.
Use Instagram endpoints to turn 社交搜索工作流 into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Instagram endpoint catalog — 5 endpoints, 14 documented request parameters, and 5 published response schemas — the same catalog Docs and Playground run against.
5 documented Instagram endpoints, grouped into 4 request families — Post, Profile and Reels, plus 1 more.
14 request parameters are documented across those Instagram endpoints, 11 of them required — the full input contract is public before you write any integration code.
5 of the 5 Instagram endpoints ship a recorded example response, and 5 carry a documented response schema — you can code against the real JSON before the first request.
Instagram endpoints document their error responses (400, 404, 429, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
5 hosted MCP tools back the Instagram endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/instagram/post/{id}/{post_id}
/instagram/profile/{username}
/instagram/reels/{id}
/instagram/user/{username}/posts
Endpoint catalog
/instagram/post/{id}/{post_id}Returns media details for an Instagram URL shortcode. Use media.code from the reels response or shortcode from a public post URL; numeric media IDs are rejected.
Response notes
- `404`: no publicly retrievable post found for the supplied shortcode. - `503`: the upstream request failed or access was denied.
MCP tool instagram_post
/instagram/post/commentsReturns top-level comments for a public Instagram post or Reel. `reply_count` is included when the logged-out source exposes it; reply bodies are not available on this anonymous surface. Pass `paging_info.max_id` back as `max_id` for the next comment page.
MCP tool instagram_comments
/instagram/profile/{username}Returns the public profile of an Instagram account by `username`. The response has the user id, full name, biography, bio links, external URL, category, follower, following and post counts, verified and private flags, location, profile picture, recent posts with captions and like counts, and related profiles.
MCP tool instagram_profile
/instagram/reels/{id}Returns up to 12 public Reels via anonymous proxied HTTP for the numeric Instagram user ID. Supports opaque `max_id` pagination. Captions, timestamps and original image dimensions are omitted when the public source does not expose them.
Response notes
- Uses Instagram's logged-out public feed through proxied HTTP, without browser rendering or account credentials. The numeric ID resolves through Instagram's own profile redirect; the returned feed must match that numeric ID. - `max_id` is opaque: pass the returned `paging_info.max_id` unchanged. Cursors issued by the earlier clips-API source are not interchangeable with the new feed; restart from the first page after the source migration. - `media.id` is the source media PK. `media.code` is the URL shortcode. - The public grid supplies thumbnails and engagement counters. Captions, `taken_at`, and original image dimensions are unavailable on this surface; those fields are omitted. Thumbnail candidate `width` and `height` are omitted when unknown. A clip may have another author while appearing in this feed. - Reels use anonymous Instagram access. An explicit upstream login denial returns `503` with `Retry-After: 30`; this does not indicate an invalid Crawlora API key. - Cold upstream failures may be served from a brief cache (30 seconds by default). Back off rather than repeatedly requesting a failing page. - A successful stale snapshot takes priority over an error. Check `X-Availability-Mode: stale` to distinguish cached data from a fresh response. A cached first page does not guarantee the next pagination page is available. - For post lookups, pass an item's `media.code` as `post_id`, not `media.id`.
MCP tool instagram_reels
/instagram/user/{username}/postsReturns public posts and Reels from the logged-out Posts tab for an Instagram username. Each item exposes the fields available in Instagram's public grid; source-omitted metrics and dimensions are not inferred. Pass `paging_info.max_id` back as `max_id` for the next page.
MCP tool instagram_user_posts
Related APIs
Social & Creator Platforms
Build creator intelligence, video research, transcript, and audience-comment workflows without maintaining YouTube scrapers.
Social & Creator Platforms
Turn Twitch's public channel, stream, clip, and team data into structured JSON — live status and viewer counts, top games, clips, VODs, and team rosters — as normalized JSON. Credential-free.
Social & Creator Platforms
Track creator and video activity, discover sounds and LIVE streams, and study public ad creatives through documented TikTok API routes.
How to scrape Instagram
Instagram 需要登录且限流严格，因此稳定地抓取它并不容易。Crawlora 的 Instagram 端点将公开的账号资料、帖子和 Reels 数据返回为结构化 JSON。
按用户名查询的公开账号资料、按短代码查询的帖子，或某个账号的 Reels。
将用户名或短代码传给 Crawlora 的 Instagram 端点——托管执行负责处理访问。
获取粉丝数、简介和帖子数量；以及每条帖子的文案、点赞数、评论数和媒体 URL。
定期重新运行以监控粉丝增长、发帖节奏和互动情况随时间的变化。
FAQ
将公开的 Instagram 用户名或帖子短代码发送给 Crawlora 的 Instagram 端点，即可获得结构化 JSON——粉丝数、简介、文案、点赞数、评论数、媒体 URL——无需维护浏览器自动化。请采集公开数据并遵守 Instagram 的条款。
可以——Crawlora 通过托管执行返回公开的账号资料和帖子数据，无需登录。它不会访问私密账号、私信或任何需要认证的内容。
在遵守 Instagram 使用条款、robots 指令、速率限制和适用法律的前提下，采集公开可访问的账号资料和帖子数据通常是被允许的。这适用于你有权采集的公开数据。
是的。Meta 的 Graph API 只能管理你自己拥有并通过 OAuth 连接的商业或创作者账号——它完全无法返回其他账号的帖子、粉丝或公开资料数据。Crawlora 的 Instagram 端点可以读取任意公开账号的公开账号资料和帖子数据，无需 Meta 应用审核或连接账号。