Instagram reel download API: oEmbed embeds, Sume imports
Instagram's oEmbed endpoint is for embedding, not downloading. Sume's POST /v1/media-imports copies a public Reel URL into Sume storage; YouTube is rejected.
Meta's Instagram oEmbed endpoint is not a download API: its page says it is "only meant to be used for embedding Instagram content in websites and apps." If you need a public Reel as a file you can reuse, Sume's POST /v1/media-imports imports a public TikTok or Instagram video URL into Sume-owned storage.
Vendor wording is from Meta's oEmbed page; import behavior is from the Sume OpenAPI description for submitMediaImportJob, read 2026-09-30.
What does Instagram oEmbed give me?
An embed, meant for display inside a website or app. Meta's page states that purpose and nothing about handing you the video bytes, so do not build a download workflow on it.
What does POST /v1/media-imports accept?
A public HTTPS TikTok or Instagram video or Reel URL. Sume creates a queued media_import job and a mimp_ resource, mirrors the bytes to media.sume.com, and records a workspace asset with status mirrored. The documented practical size cap is about 2GB.
Imports matter because Timeline 1.0 only takes this workspace's media.sume.com media; its docs say to import first. See Timeline 1.0.
Why does a YouTube URL return unsupported_platform?
The endpoint is scoped to TikTok and Instagram. The OpenAPI text says YouTube and other hosts are rejected with unsupported_platform. Treat that code as a final answer for that URL, not as something to retry.
| Instagram oEmbed | Sume `POST /v1/media-imports` | |
|---|---|---|
| Purpose | Embedding content in websites and apps | Copy a public video URL into Sume storage |
| Hosts | Public TikTok or Instagram; others rejected | |
| Result | An embed | A mimp_ job and a mirrored workspace asset |
What can I do with the imported file?
The returned URLs are URL-first inputs for generators, with no media_id gate. Make sure you have the right to reuse the video; Sume's docs do not make that call for you. For the Reel formats you are likely to render next, see Instagram Reels API video requirements.
Sources
Related posts
More in Use cases
- Instagram 3-second minimum for Reels: check clips before publishing
Meta lists Reels at 3 seconds minimum, but Sume video-trim accepts down to 0.2 s. Read duration_seconds from the trim result before you publish.
- Instagram Stories API video: 60 seconds max, trim with Sume
Meta's reference lists Stories video at 3 to 60 seconds, 100MB and 23-60 FPS. Sume video-trim writes a range at 24, 25, 30 or 60 fps to fit.
- Instagram Stories vs Reels API limits, side by side with Sume caps
Meta lists Reels at 3 s to 15 min and 300MB, Stories at 3 to 60 s and 100MB. Sume video-trim can cut either from a longer clip, up to 900 s of output.
- App Store preview video length: 15-30 s, 30 fps max
Apple's app preview specs list 15-30 seconds and a 30 fps maximum. Sume's Timeline keeps source fps when omitted, so set output fps to 30 for a preview.
Written by Sume