> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/instagram/audio-audioid-reels>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/instagram/audio-audioid-reels.mdx>

---

# Instagram audio Reels API

List public Instagram Reels that reuse a specific audio track, keyed by audio id, with cursor pagination in the shared Social Fetch envelope.

`GET /v1/instagram/audio/{audioId}/reels` takes the numeric audio id from an Instagram audio page URL (for example the trailing digits in `https://www.instagram.com/reels/audio/1392969992841787/`). The response returns `data.audioId`, optional track-level `data.audio`, a `data.reels` array, and `data.page` (`hasMore`, `nextCursor`). Each reel row includes id, shortcode, url, caption, createdAt, thumbnail/display/video URLs, hasAudio, nested metrics, dimensions, owner, and when Instagram exposes them: `videoDurationSec`, location (including lat/lng), richer audio attribution, `taggedUsers`, and `coauthors`. Reel order is Instagram's audio-page ranking, not chronological. Pass optional `cursor` when `data.page.hasMore` is true.

`thumbnailUrl`, `displayUrl`, `videoUrl`, owner `avatarUrl`, and audio cover URLs are Instagram CDN links when present — they can expire or be rejected outside the original retrieval context. This route has no `lookupStatus`. An empty `data.reels` array can mean no public Reels use the audio, or other cases. Bill from `meta.creditsCharged`. For a creator's own Reels use `GET /v1/instagram/profiles/{handle}/reels`. For keyword discovery use `GET /v1/instagram/search/reels`. For a fresh trending sample use `GET /v1/instagram/reels/trending`.

## Request

- **Endpoint:** `GET /v1/instagram/audio/{audioId}/reels`
- **Credits:** 1 credit per successful request.
- **Input:** by audio id
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/instagram/audio/audioid/reels/get)
- **Platform page:** [/platforms/instagram](https://www.socialfetch.dev/platforms/instagram)

## FAQ

### How do I list Instagram Reels for an audio track via API?

Call `GET /v1/instagram/audio/{audioId}/reels` with your Social Fetch API key (`x-api-key`) and the numeric audio id in the path. Read `data.reels` and `data.page` in the JSON response. See the API docs for parameters and examples.

### Where do I get the Instagram audioId?

From a public Instagram audio page URL. The audioId is the numeric id in paths like `https://www.instagram.com/reels/audio/1392969992841787/`. You can also pull it from Reel payloads that include audio attribution when you already resolved a post.

### How much does the Instagram audio Reels endpoint cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth. Each paginated page is a separate billed request.

### How does pagination work on Instagram audio Reels?

When `data.page.hasMore` is true, pass `data.page.nextCursor` as the `cursor` query param on the next request. Keep the same `audioId` across pages.

### What does each audio-page reel row include?

The same product fields as trending Reels — id, shortcode, url, caption, createdAt, thumbnailUrl, displayUrl, videoUrl, hasAudio, nested metrics (plays, likes, comments), dimensions, and owner — plus videoDurationSec, location (id, name, lat/lng when present), audio attribution, taggedUsers, and coauthors when Instagram exposes them. `data.audio` is the track-level object for the requested audio id (artist, title, cover, duration, asset vs cluster id). Source CDN URLs can expire.

### Are the Reels in chronological order?

No. Instagram ranks the audio page; `data.reels` follows that ranking, not `createdAt`. Sort client-side by `createdAt` if you need chronological order.

### Why is data.reels empty for an audioId that looks valid?

This route has no `lookupStatus`. An empty array can mean no public Reels use this audio, or other cases. Do not treat an empty list as a hard "audio not found" signal without additional checks.

### How is this different from profile Reels, keyword search, or trending?

This route pages Reels that reuse one audio id. `GET /v1/instagram/profiles/{handle}/reels` pages a creator's Reels tab by handle. `GET /v1/instagram/search/reels` is keyword discovery. `GET /v1/instagram/reels/trending` returns a fresh sample batch with no query. Use audio Reels when the sound is the join key for the list.

### Do I need Instagram OAuth to list Reels for an audio track?

No. You authenticate to Social Fetch with an API key. The route reads public audio-page Reel data; it does not act on behalf of a logged-in Instagram user.