graph.instagram.com 400: parameter only for Facebook Login

Requests to graph.instagram.com with a Facebook-Login-only parameter now return 400 naming it, instead of being ignored. How to read the error and fix the call.

4 min readSume
All posts

A 400 from graph.instagram.com that names a parameter means that parameter is supported only in Instagram API with Facebook Login. The Sep 28, 2026 changelog says such requests, for example with branded content or caption add-on parameters, now return a 400 naming the unsupported parameter. They were previously ignored.

Facts here are from the Instagram platform changelog, read 2026-09-30.

How do I read the error?

Find the parameter name in the 400 body, then check whether your token came from Instagram Login or Facebook Login. The page says "such as", so branded content and add-on parameters are examples, not a complete list.

Behavior change from the Meta changelog dated 2026-09-28, read 2026-09-30.
RequestBeforeNow
graph.instagram.com, Facebook-Login-only parameterParameter ignored400 naming the parameter

How do I fix it?

Either remove the named parameter, or make that call through Instagram API with Facebook Login, where it is supported. The earlier success was misleading: the parameter was ignored, so whatever it controlled never applied. Audit older calls for the same silent drop. For one concrete set of affected parameters, see poll_attachment on Reels.

Does this affect how I prepare the video?

No. The error is about request parameters, not the file. Sume video trim outputs a plain MP4 from a clip already on media.sume.com (Video trim). Reel file limits are in Instagram Reels API video requirements.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume