How-To Guide

What changed in the Instagram API in 2026?

Meta's 2026 Instagram Platform releases changed publishing labels, read fields, audio, embeds and version rules. What each date changes, and how to adopt it.

9 min read

Five groups of change matter to a publishing integration. media_url became optional for protected video on July 30. AI and paid-partnership labels moved into the publish call on June 22 and April 22. New engagement fields arrived with scope limits. The Audio API and oEmbed gained new routes. And version deprecations plus stricter error responses began failing requests that used to pass quietly. The changelog runs from February 6 to July 30, 2026, and Meta's public release feed adds September and October entries.

  • July 30: media_url is omitted for videos with copyrighted audio or downloads turned off, and requests still return 200, so treat the field as optional.
  • June 22: is_ai_generated applies the AI info label at container creation, and link_clicks reads Story link taps on Facebook Login.
  • April 22: partnership labels move into the publishing call, and reposts, saves, shares plus aggregated totals become readable on Facebook Login.
  • September and October: caption add-ons, a config_issue field, ordered ad comments and 400 errors for parameters sent to the wrong host.

The 2026 changelog at a glance

Meta's Instagram Platform changelog is the spine for this question, and it reads as a dated list rather than a narrative. The 2026 entries run from a February 6 OAuth parameter to a July 30 protection on media URLs. Meta's public release feed carries later September and October entries that the changelog page we read did not show, so treat the official page as the primary record and the feed as the supplement.

Sort the entries by what they ask of you. Most add a capability you can adopt when it helps: an OAuth flag, an attachment route, a new metric, another embed path. A smaller set changes behavior you may already depend on, and those are the entries that turn into tickets. This table is the year in that order:

DateWhat changedWhere it lands
February 6enable_fb_login parameter added to Instagram OAuth requests, default trueLogin setup
March 13Direct Send accepts attachment IDs in addition to image URLsMessaging
March 30Creator Marketplace Discovery rate limit rises from 240 to 1,000 queries per user per hour; new filters and fieldsCreator discovery
April 22Partnership label at publish time, three engagement fields, aggregated totals, Collaborative Media API, Like Media and Comments APIPublishing and reporting
May 6Sending multiple images leaves beta for all accountsMessaging
May 15Instagram oEmbed can be called without an access tokenEmbeds
June 1Instagram Audio API for searching and attaching audio, plus media_audio_typeReels publishing
June 22is_ai_generated applies the AI info label; link_clicks reads Story link tapsPublishing and insights
July 30media_url omitted for copyrighted audio and download-disabled reelsReading media

The changelog orders these newest first, which is useful for a reader checking the current state and awkward for a team planning work. Read it oldest first for a migration, and read it newest first when a field suddenly returns nothing in production.

A 2026 timeline grouped into three lanes: publish and labels, read and measure, and migrate and fix. Dates run from a February 6 OAuth flag through a July 30 media_url protection, with September and October entries from Meta's release feed placed at the end.

The year in three lanes. Built from Meta's Instagram Platform changelog and release feed read on November 18, 2026; every date names a release on one of those two pages.

Superdirector

Make it work for your brand

Find it. Remake it. Post it. Superdirector turns the viral formats in your niche into your brand's carousels, X posts and video scripts, and keeps the calendar full.

Publishing changes: labels and captions

Two labels moved into the publish call in 2026, and both change who can do the work. The first is the AI info label. Since June 22, the Content Publishing API accepts is_ai_generated when you create a media container. For a carousel you set it on the carousel container only, and the changelog says it works in both the Instagram API with Instagram Login and the Instagram API with Facebook Login. The IG Media reference also lists is_ai_generated as a readable field, so a reporting tool can tell whether a post carries the label.

The second is the paid partnership label. The April 22 release added branded_content_sponsor_ids and is_paid_partnership to the create-container call, available through the Instagram API with Facebook Login. Meta's blog describes the change plainly: third-party platforms can now publish organic posts with the Paid partnership disclosure label directly at publish time, where previously creators using scheduling tools had to add the label by hand in the Instagram app after publishing. The blog says the label supports photos, Reels, carousels and Stories, and one change card we read puts the brand tag limit at two IDs.

A publishing integration that serves creators should treat the label parameters as part of the create call, not as a follow-up edit. There is no edit step in this flow, and the old manual workaround sits outside your system. If a creator asks why a scheduled post lost its partnership label, the answer is usually that the create call omitted the parameter on the Facebook Login route.

Captions changed twice more. The September 28 release added caption add-ons: a poll with two to four options, or a comment prompt, attached to feed posts and Reels but not Stories, only on Facebook Login. A media can carry at most one add-on, and a poll runs for three days by default unless is_poll_duration_extended is set. The October 20 release made a caption set on a story container appear on the published story. Both changes enlarge what a scheduler must validate before it creates a container, because an unsupported combination now has a named error path.

Reading changes: new fields and their scope

The April 22 release added three engagement counts that Meta had not exposed before: reposts_count, saved_count and shares_count. It also added aggregated totals, total_like_count, total_comments_count and total_views_count, which combine Instagram, crossposted Facebook and boosted media and match the totals shown in the Instagram app. The blog and the changelog both scope the new counts to apps using Facebook Login. That scope is the first thing to check before you promise a client a cross-surface dashboard.

Scope narrows again at the field level. Meta's IG Media reference states that the new counts and totals are not available for carousel child media and return only for top-level objects. The media owner can disable showing likes, comments, views, reposts and shares, and the corresponding fields are then omitted. saved_count is accessible only to the media owner or an accepted collaborator. A missing field is therefore often a correct answer about privacy or media structure, not a broken request.

Three smaller read additions arrived around the same work. link_clicks counts taps on Story link stickers and is Facebook Login only. media_audio_type reports whether a video uses MUSIC from Meta's catalog or ORIGINAL_SOUND, and returns only for video media. facebook_views expanded to Feed posts and Stories, and Business Discovery view_count now combines Instagram and Facebook views for crossposted video. The October ordered_comments edge returns ad comments in Instagram display order, again on Facebook Login.

Field or edgeWhat it tells youWhere it stops
reposts_countTimes other users reposted the mediaFacebook Login only; not on carousel children; omitted if the owner hides reposts
saved_countTimes the media was savedOwner or accepted collaborator only
shares_countTimes the media was sharedFacebook Login only; not on carousel children
total_like_count, total_comments_count, total_views_countTotals across Instagram, crossposted Facebook and boosted mediaNot on carousel children; omitted when the owner hides the matching count
media_audio_typeMUSIC or ORIGINAL_SOUND for video mediaVideo only
link_clicksTaps on links in a StoryStory media, Facebook Login only
ordered_commentsAd comments in Instagram display orderFacebook Login only

The practical trap is a totals swap. A dashboard that summed like_count and comments_count can move to the total_ functions and start matching the app. If it sums those totals across carousel children, it will now overstate or skip items, because the totals are absent exactly there. Read the reference before changing the arithmetic.

A scope matrix for 2026 changes against the three Instagram API setups. The AI label is documented for Instagram Login and Facebook Login. Partnership labels, engagement fields, the Like API, link_clicks, the Audio API and caption add-ons are documented for Facebook Login. oEmbed is documented as applying to all versions. Blank cells mean the fetched pages did not state the scope.

Which setup each change is documented for. Built from Meta's changelog, the April 22 blog and the overview comparison read on November 18, 2026; a blank cell means the pages we read did not state the scope.

What now fails or needs action

The entries that break code cluster in the second half of the year. Graph API v26.0 was released on July 29, 2026, and the IG Media reference now names v27.0 as the latest version. The v26.0 changelog deprecates the Commerce Order Management API because checkout for Shops on Facebook and Instagram was sunset, and Meta states there is no replacement. Calls are blocked on v26.0 and later from July 29, and the affected surfaces are removed from all remaining versions on October 27, 2026. If your integration touches orders, that work has a deadline with no migration path.

The same version removes several legacy protocol behaviors. The pretty and debug query parameters are ignored, JSON responses are compact, requests that include date_format return an error, root requests using GET /?ids= return an error, and ETag plus 304 Not Modified behavior is gone, so requests return full responses. These are small edits individually and easy to miss in a client wrapper that has not been touched in years.

Two changes fail loudly in a useful way. On July 30, media_url became optional: a video with copyrighted or licensed audio, or a reel whose owner turned downloads off, no longer returns the field, while the request still returns 200 and the other media fields return normally. The changelog tells you to fall back to permalink or thumbnail_url. On September 28, requests to graph.instagram.com that include a Facebook-Login-only parameter began returning a 400 response that names the unsupported parameter, where those parameters had been ignored before. The same release added a config_issue field to the publish response for a publish that succeeds while dropping the caption or the user tags.

ChangeWhat now happensCode action
media_url on protected videoOmitted; response still 200Treat the field as optional and fall back to permalink or thumbnail_url
Facebook-Login-only parameter on graph.instagram.com400 naming the parameterRoute the parameter to the Facebook Login host or remove it
Caption or tagging dropped in a publishPublish succeeds with config_issue setRead config_issue and surface it instead of reporting a clean success
Commerce Order Management APIBlocked on v26.0 and later; removed everywhere on October 27, 2026Plan removal; Meta documents no replacement
Legacy protocol parameterspretty and debug ignored, date_format and root ids requests error, no 304sClean the client and retest the response parser
A four-step migration order: first handle partial publishes and wrong-host 400 errors, second add publish-time labels, third adopt read fields within their scope, fourth plan the version and commerce deprecations. A side branch separates teams publishing for their own account from teams serving other accounts.

Adopt in this order. The sequence follows blast radius rather than release date; the branch follows the scope differences in Meta's overview and changelog read on November 18, 2026.

Decide what your integration changes first

Order the work by what breaks silently. First read config_issue and the new 400 errors, because a publish that succeeds without its caption is worse than one that fails. Second add the label parameters if you publish for creators, since that work changes what the post looks like to an audience. Third adopt the read fields within their scope, because a wrong total damages a report while a missing field only leaves a gap. Fourth plan the version and commerce cleanup, which has a dated deadline and no replacement to design around.

Choose the login setup before any of that, because it decides which entries apply. Meta documents three setups: Unified Login is recommended for new integrations, Instagram Login serves accounts without a Facebook Page, and Facebook Login serves accounts linked to a Page. The overview's comparison marks content publishing and insights as supported across all three, while hashtag search, product tagging and partnership ads are not supported on Instagram Login. The 2026 additions follow the same split. The partnership label, the new engagement fields, the Like API, link_clicks, the Audio API and caption add-ons are documented for Facebook Login, and the AI label is documented for both Instagram Login and Facebook Login.

If maintaining this integration is not the product, an operated route is the alternative. Superdirector, ours, runs an account's Instagram calendar for a flat $199 per month for one AI-run operated account, with the $29 per month plan covering MCP access and hands-on creation. Publishing goes out under account-level standing permission: posting is turned on once per account, and eligible Instagram carousels and single X text posts publish under that standing permission. It is not a replacement for API access. It publishes those formats, not reels, Stories or single images, and it sends no DMs and runs no comment automation.

However you proceed, keep the two jobs apart. Adopting a 2026 change is a small, dated code edit. Keeping the integration current is a standing commitment to read changelogs, recheck field scope and retest error paths. Teams that treat the second as a product can stop reading this list; teams that treat it as a one-time migration will meet the September entries in production, one failed publish at a time.

Frequently asked questions

What changed in the Instagram API in 2026?

Meta's 2026 Instagram Platform changelog runs from a February 6 OAuth parameter to a July 30 media_url protection, and its public release feed adds September and October entries. The changes that matter to a publishing integration fall into five groups: media_url becomes optional for protected video, AI and paid-partnership labels can be set at publish time, new engagement fields arrive with strict scope limits, the Audio API and oEmbed gain new routes, and several version deprecations and stricter errors require code changes. Most additions are optional. The failures come from the entries that change an existing behavior.

What is the is_ai_generated parameter?

It is a Content Publishing API parameter introduced on June 22, 2026. Set it to true when you create a media container and the published post carries the AI info label. For a carousel, set it on the carousel container only. The changelog says the parameter works in both the Instagram API with Instagram Login and the Instagram API with Facebook Login, and the IG Media reference lists is_ai_generated as a readable field that excludes album children.

Can I add a paid partnership label through the API?

Yes, since the April 22, 2026 release, and only through the Instagram API with Facebook Login. Tag a brand with branded_content_sponsor_ids, or apply the label without a brand with is_paid_partnership, at the moment you create the container. Before that release, the blog says creators using third-party scheduling tools had to add the partnership label by hand in the Instagram app after publishing. Our read of the change cards puts the brand limit at two IDs, so check the current reference before you build a multi-brand flow.

Why are the new engagement fields empty for some media?

Three constraints in Meta's reference explain most empty responses. The fields are not returned for carousel child media, only for top-level objects. The media owner can disable showing likes, comments, views, reposts and shares, and the matching fields are then omitted. And saved_count is scoped to the media owner or an accepted collaborator, so a third-party tool reading someone else's media will not see it. Handle a missing field as a business answer, not as a failed request.

What happens to requests that use the wrong host?

Since the September 28, 2026 release, requests to graph.instagram.com that include a parameter supported only in the Instagram API with Facebook Login return a 400 response that names the unsupported parameter. The release notes say those parameters were previously ignored. A migration that silently sent branded content or caption add-on parameters to the Instagram Login host can now start failing at publish time, so route each parameter to the setup that documents it.

Did any API surface get removed in 2026?

Yes. Graph API v26.0, released July 29, 2026, deprecates the Commerce Order Management API because checkout for Shops on Facebook and Instagram was sunset, and Meta states there is no replacement. Calls are blocked on v26.0 and later from that date, and the affected surfaces are removed from all remaining versions on October 27, 2026. The same version retires several legacy protocol behaviors, including the pretty and debug query parameters and ETag-based 304 responses.

Is the Instagram API free to use in 2026?

Meta's changelog and reference pages state no price anywhere, and none of the 2026 entries introduces a fee for the Instagram Platform. This page answers what changed, not what the API costs; the cost question is a separate decision about account setup, app review, token maintenance and the publishing flow. Do not read a free API as free integration work, because the 2026 changes add migration and error-handling work of their own.

Which login setup should I build on now?

Meta recommends the Instagram API with Unified Login for new integrations. The Instagram API with Instagram Login serves accounts without a Facebook Page, and the Instagram API with Facebook Login serves accounts linked to a Page. The 2026 additions are unevenly distributed: the partnership label, the new engagement fields, the Like API, link_clicks, the Audio API and caption add-ons are documented for Facebook Login, while the AI label is documented for both Instagram Login and Facebook Login. Choose the setup first, because it decides which of these changes even apply to you.

Related practical guides

Start with the error path, not the new field

A partial publish that reports success and a 400 on the wrong host both cost more than a missing metric. Read config_issue and test the wrong-host parameter first, then add labels and fields in that order, and put the October 27, 2026 commerce removal on the calendar now.