Instagram Audio Reels API

Instagram Audio Reels

Features

• Known audio ID targetingSubmit one or more numeric Instagram audio IDs to collect public Reels associated with those exact identifiers rather than searching by title or artist.
• Independent per-audio collectionProcess every audio ID with its own results_limit, cursor sequence, and within-input record de-duplication so each source has a bounded collection.
• Source-linked Reel recordsReceive normalized Reel IDs, URLs, captions, creator identity, media, timestamps, visible engagement, and extra.audio_id provenance.

Parameters

How to Use

Submit known audio IDs as an asynchronous task, poll its task ID, then read normalized Reel records with cursor pagination.

1. Prepare one or more known Instagram audio IDs as non-empty numeric strings.
2. POST audio_ids with an optional per-audio results_limit to /v1/instagram/audio-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/audio-reels" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"audio_ids":["123456789012345"],"results_limit":20}'

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

Best Use Cases

• Audio participation review: Group public Reel URLs, captions, creators, and timestamps by extra.audio_id to review visible participation around known audio.
• Creative example research: Build a source-linked review set from captions, creator identity, media references, and original Reel URLs associated with selected audio IDs.
• Visible engagement comparison: Compare available likes, comments, views, and plays across collected Reels while retaining the audio ID that produced each record.

Pro Tips

• Resolve and verify audio IDs before submitting them; this endpoint accepts numeric identifiers and does not search for audio by song title, artist, or keyword.
• Plan volume and estimated credits per audio ID because results_limit is applied independently to every submitted identifier.
• When combining repeated collections, de-duplicate by stable Reel ID or canonical URL while keeping extra.audio_id for source attribution.
• Treat counters, media, creator fields, and timestamps as optional, and interpret collection as bounded by the per-audio limit, feed end, or 100-page ceiling rather than a complete historical archive.

Related APIs