# Instagram Audio Reels API (https://www.socialcrawl.dev/platforms/instagram/audio-reels)

> Returns reels that use a specific audio track on Instagram. Each reel includes engagement metrics and author info. The `audio_id` is the `post.ext.music_id` a reel carries on /v1/instagram/post and /v1/instagram/profile/reels, or on /v1/instagram/profile/posts with include=audio, so reels that share a sound can be expanded into every other reel using it. On the first page `data.total` is the number of reels Instagram shows for the sound, or null when that count is not available, and later pages leave it null. On the first page `data.is_trending` is `true` when Instagram currently marks the sound as trending in Reels and `false` when it does not; it changes over time, later pages leave it null, and it is null when that signal is not available. On the first page `data.sound` describes the sound itself as `{ track_title, artist, is_original, creator_username, created_at, duration_seconds, is_explicit, spotify_track_id, first_reel_url }`: on an original sound `creator_username` is the account that created it, `created_at` is when it was created and `first_reel_url` is the reel it was first used on, while on a licensed track those three are null and `spotify_track_id` is filled when Instagram links the track to Spotify; `data.sound` is null on later pages and when the sound's details are not available. When `audio_id` is a cluster id, `data.total` counts every upload in the cluster and `data.sound` describes the one upload Instagram shows for it, so its creator is not necessarily the cluster's first user. To record `data.total` every day, create a Monitor that tracks `total`; see /docs/recipes/track-sound-growth. Each reel carries `post.ext.audio_cluster_id`, Instagram's audio cluster for that reel: the id Instagram uses to group different uploads of the same sound. It is absent on a reel when it is not available. A page carries up to about 12 reels, in the order Instagram's own audio page lists them, which is not by date. Pass `pagination.next_cursor` back as `cursor` to request the next page. A page that comes back empty is not charged. On a reel also posted to Facebook, `engagement.views` can include its Facebook views: `post.ext.instagram_views` is the Instagram-only figure, the same on every Instagram endpoint, and `post.ext.facebook_views` is the Facebook part when the source reports it.

TL;DR: `GET /v1/instagram/audio/reels` costs 1 credit per call and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `audio_id` | yes | Instagram audio ID: the numeric id from an instagram.com/reels/audio/{audio_id}/ URL |
| `cursor` | no | Pagination cursor. Use the `next_cursor` from the previous response to fetch the next page. |
| `since` | no | Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off each page. This list is not in date order, so the walk does not stop at the date: keep following `next_cursor`, and each page costs what a page costs even when every row on it is filtered out. A row with no date is kept. `published_after`, `start_date`, `from_date`, `publish_time` (`yesterday`, `this-week`, `this-month`, `last-3-months`, `last-6-months`) and `max_age_days` are accepted and applied as `since`. |
| `until` | no | Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. `published_before`, `end_date` and `to_date` are accepted and applied as `until`. |
| `max_pages` | no | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. |
| `max_items` | no | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. |
| `max_credits` | no | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. |

## Code example

```bash
curl -G "https://www.socialcrawl.dev/v1/instagram/audio/reels" \
  --data-urlencode "audio_id=1392969992841787" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### How do I get reels that use a specific sound with an API?

Send a GET request to /v1/instagram/audio/reels with the audio_id parameter. SocialCrawl returns a JSON array of reels using that audio track including author, caption, view count, and media URLs.

### Where do I find the audio_id to pass in?

Call /v1/instagram/search/music or /v1/instagram/music/trending first. Each track carries an audio id that you feed straight into this endpoint as audio_id.

### How do I page through more reels for a sound?

Each response includes a cursor. Forward it as the cursor parameter on your next request to fetch the following page of reels that use the same audio.

### Why is this endpoint cheaper than the search endpoints?

It is a standard endpoint at 1 credit per request because it looks up reels for a known audio id rather than running a heavier search. The music search endpoints are 5 credits.

### How much does the Instagram Audio Reels API cost?

It costs 1 credit per page returned (standard tier). New accounts get 100 free credits, so you can pull around 100 pages before deciding to top up.

See the full Instagram API: https://www.socialcrawl.dev/platforms/instagram

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- How to find Instagram reels that use a specific sound with an API
- Instagram audio reels API for tracking how a trending sound spreads