Social Media API Report 2026: most of X's breaking changes came with five days' notice or less

Key findings

1. 34 breaking changes in a 24-month window, 13 of them to posting. The rest hit what an integration does around the post: metrics, comments, messaging, webhooks, sign-in and engagement actions.
2. X and Instagram tie for the most, 7 each, and differ most on warning. 4 of X's 6 dated breaking changes gave five days or less. Instagram's 6 dated ones gave 90 to 132 days.
3. 5 of the 20 dated breaking changes gave a week or less, and 4 of those were X. The median across all 20: 90.5 days.
4. 14 of 34 came without an exact date to measure notice from. The platform published no exact effective date (some said only "within the next 1-2 weeks" or a month) or no announcement date, the change applied only on a newer API version, or the changelog entry was written after the change had shipped.
5. Bluesky's sources document no breaking changes, and Bluesky raised its upload limits 3 times. YouTube cut the quota cost of an upload from about 1600 units to about 100.
6. LinkedIn retired 25 API versions inside the window, roughly one a month, and Facebook retired 6 Graph API versions. These are scheduled, so they are counted separately from breaking changes.
7. On X, a post containing a URL costs about 13 times a plain one: $0.200 against $0.015.
8. Reddit is closing its public Data API. New requests stop on 2026-10-31, closures begin on 2027-01-12, and the rest end in March 2027.

Check your stack

Pick the platforms you build on. Everything below is computed from the same verified data as the rest of this page.

How much notice developers got

Each dot is one breaking change with both an announcement date and an effective date in the platform's own source. Platforms are ordered by their median notice, shortest first.

X gave the least notice

X's breaking changes across the whole window, with the notice each one carried. Separately, X launched pay-per-use pricing in February 2026 and moved legacy Basic and Pro subscribers onto it after June 1 and September 1, 2026.

• No exact date Command-style chunked upload on v2 POST /2/media/upload (command=INIT/APPEND/FINALIZE) deprecated in favor of dedicated initialize, append and finalize endpoints. The post says 'within the next 1-2 weeks' and gives no date. Source
• 34 days DM events: MessageCreate no longer includes participant_ids array. SourceSource 2
• 104 days v1.1 media upload endpoints sunset for self-serve developers (Free, Basic, Pro) on 2025-06-09, forcing a move to the v2 media upload endpoints. SourceSource 2
• Same day POST /2/users/:id/likes and POST /2/users/:id/following removed from the Free tier, effective immediately. Paid tiers unaffected at that time. Source
• Same day Programmatic replies via the API only permitted when the replier is summoned by the original author (@mention or quote). Programmatic @mentions/quotes of non-participants restricted. SourceSource 2
• 5 days Account Activity replay endpoint POST /2/account_activity/replay/webhooks/{webhook_id}/subscriptions/all deprecated effective March 25, 2026. Use POST /2/webhooks/replay. Source
• 4 days Following, Likes and Quote-Posts via API removed from all self-serve tiers, effective 2026-04-20. Source

Pricing tightened too. In April 2026 X raised the price of a post from $0.01 to $0.015, and a post containing a URL now costs $0.200, paid from prepaid credits.

Breaking changes by platform

What it takes to post for someone else

Most platforms put posting for other people behind a review or audit. On TikTok, YouTube (for projects created after 28 July 2020) and Pinterest, even posts to your own account stay private until it clears, and on Facebook, test posts made in Development mode are visible only to people with a role on the app. So a first integration can look like it worked while nobody else can see the result.

Reddit is closing its public API

1. 11 Nov 2025 Self-service access to the public Data API ends. New access needs approval under the Responsible Builder Policy.
2. 30 Sep 2026 Reddit staff announce the closure dates.
3. 31 Oct 2026 New requests for public Data API access are no longer accepted.
4. 12 Jan 2027 Access starts to close for apps and users that have not registered or responded to outreach.
5. Mar 2027 Remaining public API access ends. Reddit has not given a day.

Blotato does not post to Reddit. It is in this study because Reddit is withdrawing its public API altogether.

Versioned APIs retire versions on a clock

LinkedIn and Meta version their APIs and retire old versions on a published schedule. LinkedIn's versioned releases follow a monthly cycle, and 25 versions sunset inside the window. Facebook retired 6 Graph API versions. A sunset is predictable, so this study counts it separately from breaking changes, but what happens on the date differs. On LinkedIn, a request carrying a retired version header returns an error. On Meta, calls to a version that is no longer usable are defaulted to the next oldest usable version, so they keep answering, just not from the version the integration was built and tested against.

Posting limits, and the caps Blotato adds

The last column is Blotato's own cap, applied on top of whatever the platform allows. We publish it because a limits table that leaves out the tool's own number leaves out one that users actually hit.

Where the docs disagree

Reading every page side by side turned up places where a platform's own documentation disagrees with itself, or where guidance reversed within weeks. We report both sides rather than pick one. One of them is ours.

The full change log

All 130 documented changes in the window, newest first, each linked to the platform's own source. The same data is in the CSV, with a notes column carrying every dating detail.

What this means if you build on these APIs

Every row above lands on whoever maintains the integration. Build directly on nine platform APIs and that is you: each platform's approval rules, version calendars on LinkedIn and Meta, and on X, changes that can take effect the week they are announced.

A hosted API moves much of that work to the vendor. That is what Blotato sells, so weigh this paragraph accordingly: one key reaches 9 platforms through accounts you connect and authorize on each platform, and keeping those integrations working through changes like the ones in this log is our job. It does not remove platform rules, which still apply to every post. Our own caps are in the table above, and Blotato's comments, messages and DM automation cover Instagram and Facebook only. The social media API page covers each platform, and our pricing study compares what social media tools charge when an AI agent posts through their API or MCP server.

Method

• Window. Changes announced or taking effect between 2024-10-01 and 2026-09-30. Reddit announced its closure inside the window for dates after it, so it is included, and because Reddit set two separate steps (apps that have not registered from 2027-01-12, all remaining access in March 2027) it counts as two changes. Pinterest's move to continuous refresh tokens also counts as two: removing the refresh_on parameter (February 2025) and ending support for the legacy token (stated September 2025).
• Sources. Only each platform's own developer docs, changelogs, revision histories, developer blogs, help centres, terms and staff posts on its own forums. Third-party coverage was used to find leads, never as a source.
• Evidence. Every fact carries a verbatim quote from its source, and a script confirmed each quote appears on the saved page. A second, independent pass then re-fetched every source live, checked that each claim says no more than its quote, and searched for changes the first pass missed.
• Scope. Changes that affect posting, published-content metrics, comments and messaging, authentication, access tiers or price. Excluded: oEmbed, generic Graph API protocol features, a Pinterest user-interests endpoint, Reddit's unauthenticated reads and X's Activity API profile events.
• Definitions. Breaking: a previously working call fails or code must change. Tightening: a higher price, new gate or lower limit while existing calls keep working. Loosening: a limit raised or a cost cut. Removing or renaming a field an integration sends or reads, or a format change the platform says requires code changes, counts as breaking. Version sunsets under a published versioning policy are counted on their own. Changes to what a call returns without changing its shape, and omitting optional fields that were returned as null, count as neutral.
• Notice. Computed only where the source states both dates. "Same day" appears only where the source says the change was immediate. Month-level dates (LinkedIn release notes) carry no notice figure. Where a source says a change happens "by" a date, the notice is an upper bound and is labelled "up to". For Meta changes that applied to the newest API version on announcement and to all versions on a later date, notice is measured to the all-versions date, the point at which an integration on an older version stops working. Changes that applied only to newer versions, with no all-versions date, are marked version-gated.
• Hit posting. A change counts as hitting posting when it touches the publishing endpoints, or the tokens and permissions a posting app uses to publish. User sign-in changes, such as TikTok's Login Kit, count as other surfaces.
• Limitations. The counts are a floor: they cover what each platform documented, and TikTok's changelog says it is not exhaustive. Bluesky's limit changes are dated by protocol commits, because no deploy date is published.