Instagram search_posts API

一次 REST 呼叫取得 Instagram search_posts 資料——以 FetchPI 全平台共用的穩定 JSON 結構標準化輸出。

1 個已發布端點
GET /v1/ig/search/posts

契約摘要（英文）: Search Instagram posts (capability ig.search_posts)

標準化回應實體: instagram/search_posts
capability: ig.search_posts

每個回應都附帶新鮮度（cache / default / live）與計費中繼資料。

使用場景

按關鍵字搜尋 {{platform}} 內容與帳號，回傳標準化結果，直接可用於評分排序。
追蹤熱門話題與熱榜，第一時間掌握新興討論。
對搜尋與趨勢查詢建立告警，讓團隊即時掌握變化。

回應欄位

Instagram reel search response (normalized envelope)

Response envelope for GET /v1/ig/search/posts (capability ig.search_posts). The upstream surface is v2/search_reels: results are reel-type posts ONLY (photo posts are not covered by this search); echoes the effective query.

欄位	類型	必填	說明
query	string	可選	Echo of the effective search query.
data	post[]	必填	—
next_cursor	string \| null	必填	Opaque pagination cursor; null when results are exhausted. Cursor validity is tied to the provider that produced the page.
meta.request_id	string	必填	—
meta.freshness.mode	cache \| default \| live	必填	—
meta.freshness.age_seconds	integer \| null	可選	—
meta.freshness.source_layer	cache \| db \| upstream	必填	—
meta.freshness.stale	boolean	可選	—
meta.billing.cache_hit	boolean	必填	—
meta.billing.amount_credits	integer	必填	Credits actually charged for this request (the settlement unit; 1 credit = $0.0001, permanent).

欄位備註為契約英文原文。

回應中繼資料

欄位	類型	必填	說明
mode	cache \| default \| live	必填	Effective mode after merging param > max_age > source policy (D-004).
age_seconds	integer \| null	可選	Age of served data; null when unknown.
source_layer	cache \| db \| upstream	必填	Which layer served the response (PRD §10).
stale	boolean	可選	True when stale data was served under stale_if_error / SWR (D-004).
billing.amount_credits	integer	必填	Micro-USD (1e-6 USD) actually charged for this request.
billing.cache_hit	boolean	必填	—

欄位備註為契約英文原文。

請求與回應範例

GET/v1/ig/search/posts

curl -H "Authorization: Bearer $MESHDATA_API_KEY" \
  "https://api.fetchpi.com/v1/ig/search/posts?q=meshdata"

{
  "data": [
    {
      "id": "Creel00001",
      "platform": "instagram",
      "type": "post",
      "author": {
        "id": "5566778899001",
        "username": "datafan",
        "display_name": "Data Fan",
        "verified": true
      },
      "text": "search hit one",
      "created_at": "2026-09-15T10:00:00Z",
      "metrics": {
        "likes": 341,
        "comments": 12,
        "views": 88231
      },
      "attachments": [
        {
          "type": "video",
          "url": "https://cdn.example.com/reel1.mp4",
          "duration_ms": 32500
        }
      ],
      "fetched_at": "2026-09-18T09:05:00Z"
    }
  ],
  "next_cursor": null,
  "meta": {
    "request_id": "req_01HTXQ8Z9HTQ",
    "freshness": {
      "mode": "live",
      "age_seconds": 0,
      "source_layer": "upstream",
      "stale": false
    },
    "billing": {
      "amount_credits": 300,
      "cache_hit": false
    }
  }
}

免費試用

註冊免費帳號、取得 API Key，即可在瀏覽器版 Playground 直接呼叫該端點。

在 Playground 試用

該端點的參數表、錯誤碼與回應語義見 API 文件。

查看端點參考

常見問題

cache 與 live 新鮮度有什麼不同？

cache 直接回傳已存快照、不觸及上游；live 查詢較新的資料，可能產生額外點數費用——詳見文件的新鮮度說明。

可以免費試用該端點嗎？

可以——註冊帳號、取得 API Key 後，即可在主控台的 Playground 呼叫該端點。

search_posts 能力怎麼計費？

Data API 按請求以點數計費，cache/live 新鮮度有不同倍率。目前各能力的價格以價格頁為準。

價格

按請求以點數計費，支援 cache/live 新鮮度選項——最新價格以價格頁為準。

查看價格瀏覽全部 API