instagram

List Instagram reels using an audio track

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.

get/instagram/audio/reels

Request

  • Base URL: https://www.socialcrawl.dev/v1
  • URL: https://www.socialcrawl.dev/v1/instagram/audio/reels
  • Auth: API key in header x-api-key

Query parameters

audio_idstring required

Instagram audio ID: the numeric id from an instagram.com/reels/audio/{audio_id}/ URL

cursorstring

Pagination cursor. Use the next_cursor from the previous response to fetch the next page.

sincestring

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.

untilstring

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.

Headers

Cache-Controlstring

Send no-cache to bypass the response cache and force a live fetch. Billed at the normal endpoint cost; the fresh result is written back to cache for the next caller. Only the no-cache directive triggers this. See the Response Schema guide for details.

Idempotency-Keystring

Optional UUID that makes the request safely retriable. The key is reserved atomically per account before billing. A concurrent retry receives 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After of 1 second while the original is young, growing to a quarter of the time it has been running (at most 30); a crashed reservation expires after 5 minutes. A replay keeps the cached payload immutable except for billing metadata: credits_used becomes 0, idempotent_replay becomes true, and credits_remaining is refreshed to the current balance. A known current balance appears in both the body and X-Credits-Remaining header; no balance row resolves to 0. On a transient lookup failure, body credits_remaining is null and X-Credits-Remaining is omitted. Completed outcomes expire after 24 hours. If the claim store is unavailable, the request fails closed before billing. GET endpoints do not combine idempotent replay with Server-Sent Events: use Accept: application/json when sending this header. The unsupported key-plus-SSE combination is rejected before billing.

Response

Successful response

successboolean required

Whether the request succeeded

platformstring required

Platform name

endpointstring required

API endpoint path

credits_usedinteger required

Number of credits consumed

credits_remaininginteger nullable required

Current account balance, or null when this response could not establish one. Free cache hits always return null because they do not establish an authoritative post-request balance. An idempotency replay also returns null when its current-balance lookup fails. It is never a fabricated zero, so a zero here means the account really is empty. The authoritative reading is the one on a billed response, which comes straight from the deduction.

request_idstring required

Unique request identifier for support

cachedboolean required

Whether the response was served from cache

idempotent_replayboolean

True only when this response is an idempotency replay

Example response

{
  "success": true,
  "platform": "instagram",
  "endpoint": "/v1/instagram/audio/reels",
  "credits_used": 1,
  "credits_remaining": 4999,
  "request_id": "req-abc123",
  "idempotent_replay": true,
  "meta": {
    "hint": {
      "code": "search_multi",
      "message": "You searched \"matcha\" on 3 platforms one call at a time; /v1/search/multi returns each platform's own search rows in one call at the same price per platform, and a platform with no rows is not charged.",
      "method": "GET",
      "path": "/v1/search/multi?query=matcha&platforms=instagram,tiktok,youtube"
    }
  },
  "pagination": {
    "next_cursor": "sc.eyJ2IjoyLCJjIjoiMiIsInAiOiJwYWdlIn0",
    "has_more": true,
    "page_size": 30,
    "stopped_at": "known_id"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.