Instagram Graph API version and sunset tracker (2026)

v27.0. Instagram and Facebook publishing both run on Meta’s Graph API, and Meta’s changelog names v27.0 as the latest version; the newest dated row in its version table is v26.0, introduced on 29 July 2026. Meta supports each version for about two years and runs several at once, so an app picks a version in its request URL and moves forward before that version’s sunset date.

Each platform’s own versioning, as of 5 November 2026:

Through a LinkedIn-Version header in YYYYMM form. LinkedIn publishes a version every month and supports each for at least a year, so an app sends the version it was built for and must move forward before that version sunsets; a request with no version header, or a retired one, returns an error. The newest version is 202610 (October 2026), and 202511 sunsets on 16 November 2026. See the LinkedIn posting API guide.

Telegram and Bluesky. Telegram’s Bot API (10.3, 24 August 2026) only adds fields, keeping old ones marked deprecated rather than removing them. Bluesky’s AT Protocol has no version numbers at all: each method has a namespaced identifier such as app.bsky.feed.post, schemas are only extended, and a breaking change gets a new identifier while the old one keeps working.

Track each platform’s changelog, test on the newest version well before the sunset date, and move one platform at a time. A scheduler handles this for you: SkedCast keeps every network on a supported version so scheduled posts keep publishing, and the state of social publishing APIs 2026 report covers the other differences, from access to retries. Token lifetimes are in access token expiration by platform.