Instagram Platform changelog 2026: four changes for Reels pipelines

Meta's Instagram Platform changelog lists May and June 2026 changes: oEmbed without a token, Audio API, media_audio_type and is_ai_generated. What each means.

5 min readSume
All posts

Meta's Instagram Platform changelog for 2026 has four entries that touch a Reels pipeline: multi-image messaging leaving beta on May 6, oEmbed working without an access token on May 15, the Audio API and media_audio_type on June 1, and the is_ai_generated parameter on June 22. Only the last three matter to a Reels workflow, and each needs a small code change.

Dates and wording come from Meta's changelog page, read 2026-10-02. The Graph API version note comes from Meta's versions page. Where Sume has an existing post on a change, we link it instead of repeating it.

What changed, by date?

This table lists the entries as the page stated them.

Instagram Platform changes, May to June 2026 (read 2026-10-02)
DateChangeWhy a Reels team cares
May 6, 2026Sending multiple images in messages exited betaNot a Reels change; DM tooling only
May 15, 2026oEmbed can be called without an access tokenEmbedding public Reels needs no token
June 1, 2026Audio API launched; media_audio_type returns MUSIC or ORIGINAL_SOUNDAudio lookup and reading what a Reel used
June 22, 2026is_ai_generated parameter on Content PublishingApply the AI info label when publishing

What do I change for AI-generated Reels?

If any part of a Reel came from a generator, set is_ai_generated at container creation. Meta's wording is that it lets you "apply the AI info label" when publishing. The changelog does not say when you are required to set it, so read the label policy before deciding. The details are in the is_ai_generated post.

Sume generates the video; it does not decide your disclosure obligations. Keep a flag per artifact in your own records so the publishing step can set the parameter without guessing.

What changed for audio?

The Audio API lets apps search for and retrieve audio, including original sounds from Reels and royalty-free music, and the changelog ties it to Reels ads with copyright replacement. media_audio_type on IG Media returns MUSIC or ORIGINAL_SOUND for video content.

For a publishing pipeline the practical use is reading what a published Reel used, not choosing audio at upload. See Instagram Audio API for Reels ads and media_audio_type.

Which Graph API version should I call?

Meta's versions page lists v26.0 released July 29, 2026 and v25.0 released February 18, 2026, with a listed expiration date for v25.0 of July 29, 2028 and none yet for v26.0. Pin a version in the URL, as in graph.facebook.com/v26.0/..., and review the changelog before moving it.

Treat the expiration column as Meta's current statement, not a promise; re-read it when you plan an upgrade.

Where does Sume fit in all this?

Sume is upstream of every one of these calls: it produces or edits the MP4, and its docs describe probing a clip with video inspect before you publish. It does not call the Audio API, label content on your behalf or read your insights.

The metrics side of the same platform page is covered in views, crossposted_views and facebook_views.

What should I do this week?

Open your publishing code and check three things. Does it pass is_ai_generated for generated clips? Does it send an access token to oEmbed that it no longer needs? Does it pin a Graph API version rather than relying on a default?

Then add a monthly reminder to re-read the changelog. The entries are short, dated and easy to scan, and the cost of missing one is usually a confusing error weeks later. Keep a note of which changes you chose to ignore and why.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume