Instagram Trending Reels API

Instagram Trending Reels

Features

• No-selector feed snapshotCapture the current Reel set exposed by the trending feed without supplying a query, account, hashtag, region, or date filter.
• Normalized Reel recordsReceive Reel identity, public URLs, captions, author context, media metadata, timestamps, and visible like, comment, view, and play counts in one shape.
• Duplicate suppressionCollapse repeated feed rows by Reel ID, primary key, or shortcode before the normalized records are saved.

Parameters

How to Use

Submit an empty JSON object as an asynchronous task, poll its task ID, then read the saved snapshot records with result cursor pagination.

1. Prepare an empty JSON object.
2. POST the request body to /v1/instagram/trending-reels.
3. Poll /v1/tasks/{task_id} until the status is succeeded or failed.
4. Read /v1/tasks/{task_id}?limit=50 and follow results.next_cursor while results.has_more is true.

curl -X POST "https://api.socq.ai/v1/instagram/trending-reels" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is true

Best Use Cases

• Current discovery inventory: Save Reel IDs, public URLs, captions, creator identity, and collection times as a reviewable record of the current feed snapshot.
• Short-form creative review: Inspect caption text, author context, thumbnails, video references, dimensions, and duration to review the creative examples present in one snapshot.
• Within-snapshot engagement comparison: Compare visible likes, comments, views, plays, and creation times across the Reels returned by the same collection task.

Pro Tips

• Send an empty object only; query, region, username, hashtag, date, and results_limit fields are rejected.
• Treat each response as the source-defined feed snapshot at collection time, not as an official ranking formula or a claim of global or regional coverage.
• Do not request an upstream next page; results.next_cursor only continues through records already saved for the completed task.
• When retaining repeated snapshots, de-duplicate across tasks with stable Reel IDs or URLs because duplicate suppression applies within each feed response.
• Store collected_at with each result when building your own time series because this endpoint does not provide historical snapshots or scheduling.
• Handle captions, author fields, counters, media, URLs, and creation times as nullable public fields.

Related APIs