Instagram Graph API version and sunset tracker

Meta's Graph API v26.0 is current, introduced July 29, 2026; versions are supported for a minimum of roughly 2 years, with sunset pegged to the successor version's release, and multiple versions run concurrently. v20.0 sunsets around September 24, 2026. No distinct Threads-specific version number could be confirmed — it likely rides on Graph API's own versioning, but this is not explicitly stated anywhere in Meta's documentation, so do not print a specific Threads version number as fact.

LinkedIn's LinkedIn-Version header is currently 202609 (September 2026), confirmed on a documentation page updated just one week before this page's check date — LinkedIn revises this monthly and supports each value for a minimum of one year. YouTube Data API v3 remains current and actively revised (confirmed revision-history entries as recently as September 2026); no v4 has been announced and no v3 sunset notice exists.

X's v2 is the current organic-posting API. Its v1.1 media-upload endpoints were formally announced for deprecation, with the original mid-2025 deadline extended at least twice per forum posts; secondary sources claim the v1.1 host was still reachable as of around August 2026 with no fixed final sunset date, but this specific "still works" claim could not be confirmed via a direct primary-source fetch and should be re-verified before relying on it.

Pinterest's v5 is the sole current, supported API version. v3 is confirmed deprecated (cutover began mid-2023). v4's exact sunset date could not be found, and Pinterest's migration-guide page returned a 404 on direct fetch — possibly retired once earlier versions fully sunset, but don't assume that permanently without re-checking. TikTok's Content Posting API endpoints are versioned under /v2/; no v3 or any deprecation-of-v2 notice was found, though this evidence is weaker — it is inferred from the endpoint path rather than an explicit "current version" statement, since TikTok does not appear to publish a changelog/sunset page equivalent to Google's or Meta's.

Bluesky's AT Protocol has no numbered REST-style versioning at all. Methods are identified by a reverse-DNS namespaced identifier (NSID, e.g. app.bsky.feed.post) rather than a version segment in the URL. A breaking change requires minting an entirely new NSID — the old one stays frozen and functioning, and existing schemas may only be extended additively, never modified in place. This is architecturally distinct from every other platform surveyed here and should be stated plainly, not treated as an odd exception to the conventional model.

Telegram's most recently confirmed-dated Bot API release is 10.2 (July 14, 2026); evidence of a further 10.3 release exists via third-party client-library tracking, but its exact date could not be confirmed from a primary source. Telegram ships updates roughly every 1-3 months and has never been observed to formally sunset a prior Bot API version — old fields are kept and marked deprecated rather than removed, a strictly additive, backward-compatible model.