> **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/v2-instagram-reels-trending>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/instagram/v2-instagram-reels-trending.mdx>

---

# Instagram trending Reels API

Pull a fresh batch of the Reels Instagram is trending right now, as the same media object every v2 endpoint returns — with no filters and no pagination.

`GET /v2/instagram/reels/trending` takes no parameters (any query parameter is a `400` naming it). Authenticate with your Social Fetch API key (`x-api-key`) and read `data.media`: each item is the shared v2 media object with `kind` set to `reel` — a digit `id`, `shortcode`, `url`, `caption`, `createdAt` (ISO-8601), `owner` as a profile summary, `metrics` (`playCount`, `likeCount`, `commentCount`), `imageUrl`, `thumbnailUrl`, `videoUrl`, `dimensions` and `audio`. Every field is always present and `null` when Instagram doesn't say; trending items carry no `durationSec`, tags or location. There is no cursor and no `page`: repeat the request for another fresh batch, and expect some overlap between batches.

This feed is intermittently unavailable on Instagram's side. When it is, the call answers `503 temporarily_unavailable` with a `Retry-After` header and charges nothing, so retry the same request after a few seconds. Bill from `meta.creditsCharged`.

It is a trending sample, not an explore index. Keyword Reel search is `GET /v2/instagram/reels/search`, a creator's Reels are `GET /v2/instagram/profiles/{profile}/media` with `tab=reels`, and the curated posts of a topic are `GET /v2/instagram/topics/{topic}`.

## Request

- **Endpoint:** `GET /v2/instagram/reels/trending`
- **Credits:** 1 credit
Failed requests are free
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v2/instagram/reels/trending/get)
- **Platform page:** [/platforms/instagram](https://www.socialfetch.dev/platforms/instagram)

## FAQ

### How do I get trending Instagram Reels via API?

Call `GET /v2/instagram/reels/trending` with your Social Fetch API key (`x-api-key`). There are no parameters. Read `data.media`. Full response shape and examples are in the API docs.

### How much does the Instagram trending 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.

### Does trending Reels paginate with a cursor?

No. Each call returns one batch, with no `cursor` and no `page`. Call the same path again for another fresh batch; some overlap across calls is expected.

### Why did I get a 503?

The trending feed is intermittently unavailable. A `503 temporarily_unavailable` charges nothing and carries a `Retry-After` header, so retry the same request after a few seconds. Keep a short retry loop with a little backoff in your client.

### Can I filter trending Reels by hashtag or date?

Not on this path — it accepts no query parameters. For tag-led discovery use `GET /v2/instagram/hashtags/{hashtag}/media`. For free-text Reel search use `GET /v2/instagram/reels/search`.

### Do I need Instagram Graph API access for trending Reels?

No. Social Fetch returns a public trending batch for enrichment-style lookups. Meta's Instagram Graph API is for accounts you manage or that grant your app access — not an arbitrary explore sample.