Log inStart Free Trial
easyCoexistence Official APIs

Facebook Graph API changes in 2026: what stopped working and what to do

In 2026 Meta released Graph API v26.0 on July 29, removed v19.0 on May 21 and v20.0 on September 24, retired reach metrics such as page_impressions_unique by June 15, ended three Messenger message tags on April 27, and on October 27 extended v26.0's changes to all remaining versions: date_format and GET /?ids= now return errors, and the Commerce Order Management API is gone.

easyCoexistence connects Pages through its own Meta app and sets the Graph API version its tools call, so your AI keeps publishing, replying to comments and DMs and reading insights through the same MCP tools while Meta's changes land, with each connection checked every 6 hours and an email when it needs reconnecting.

Oct 27, 2026

When v26.0's protocol changes reached all remaining versions: date_format and GET /?ids= requests return errors.

Sep 24, 2026

When Meta deprecated and removed Graph API v20.0; v21.0 follows on January 21, 2027.

Jun 15, 2026

The date Meta's Page Insights guide gives for deprecating page_impressions_unique and other reach metrics in all versions.

Oct 9, 2026

When Meta retired Access Verification for Tech Provider apps; Business Verification and App Review still apply.

Next oldest

Where Meta sends the calls made to a Graph API version that is no longer usable.

What changed in the Graph API in 2026, newest first?

These are the dated entries in Meta's Graph API, Pages API and Messenger Platform changelogs, and on its developer blog, that touch a Facebook Page integration, with the newest first; the sections below give what each one breaks and the fix:

Oct 27, 2026v26.0's protocol changes and the Commerce Order Management removal reach all versions
Oct 9, 2026Access Verification retired for Tech Provider apps
Sep 24, 2026Graph API v20.0 deprecated and removed
Jul 29, 2026Graph API v26.0 released; legacy Page fields fail on it
Jun 15, 2026Page, post, video and story reach metrics deprecated
May 21, 2026Graph API v19.0 deprecated and removed
May 19, 2026metadata=1 stops returning field metadata in all versions
Apr 27, 2026Three Messenger message tags return error 100
Feb 18, 2026Graph API v25.0 released, announcing the June metric removals
Jan 26, 2026Graph API v18.0 reaches its end date

What stopped working on October 27, 2026?

Two of v26.0's changes reached all remaining Graph API versions that day. Five legacy protocol behaviors went: pretty and debug are ignored, date_format returns an error, root requests to GET /?ids= return an error, and If-None-Match is ignored, with ETag headers and 304 Not Modified responses removed; debug_token is unaffected. The Commerce Order Management API, GET /{page-id}/commerce_orders included, was removed with no replacement once Meta sunset direct checkout for Shops. The fix: convert dates in your own code, request objects one by one or in a batch, and expect full responses.

Which legacy Page fields stopped working?

On Pages in the New Pages Experience, current_location, genre, network, parking and start_info are deprecated because Meta no longer maintains them, and the auto_publish_page_info_updates setting is gone from the Page settings edge. On v26.0 and later, asking for any of these fields returns a version error; Meta's changelog says the change reaches all versions about 90 days after v26.0's launch, on a date it has not confirmed. Regular Pages are not affected, and there is no replacement, so remove the fields from your requests.

What did the end of Access Verification change?

Tech Provider apps no longer go through it. Meta's post of October 9, 2026 removes the Access Verification form, its prerequisites and its status field from the App Dashboard, and endpoints that rejected calls from businesses without a passing status no longer check. Business Verification is still required before an app reaches data owned by other businesses, App Review still applies to advanced permissions, and the Data Use Checkup and Data Protection Assessment rules are unchanged. There is nothing to migrate: drop the step from onboarding plans.

What happens to calls on Graph API v20.0 now?

They are answered by an older version that is still usable: once a version is no longer usable, Meta defaults its calls to the next oldest usable one, so v20.0 calls have run on v21.0 since September 24, 2026, and v19.0's moved on May 21. They keep getting answers, under the newer version's behavior. v21.0 is itself removed on January 21, 2027, while v25.0 stays available until July 29, 2028, so move to v26.0 or v25.0 and test, rather than relying on the default.

How do versioned changes reach older versions?

In two steps, which is why one change often has two dates. A versioned change applies at once to the new version, usually with a date for the others: v26.0's protocol changes hit v26.0 calls on July 29, 2026 and all remaining versions on October 27. Out-of-cycle changes apply to all versions when introduced, and Meta's out-of-cycle log lists none for 2026. Meta keeps each version working for at least two years, and an unversioned call uses the version set in the App Dashboard.

Which insights metrics stopped working in June 2026?

The reach and impression metrics of Pages, posts, videos and stories, deprecated in all versions; requesting one returns an invalid metric error. Meta's Page Insights guide dates it June 15, 2026, while its v25.0 changelog had tied the removal to v26.0's release. The replacements Meta names:

  • page_impressions_unique and the page_posts_impressions family: page_total_media_view_unique, or page_media_view for paid and organic breakdowns.
  • post_impressions_unique and its paid, organic and viral variants: post_total_media_view_unique, or post_media_view for breakdowns.
  • 3-second viewers such as page_video_views_unique and post_video_views_unique: the same viewer metrics.
  • Video impressions such as total_video_impressions: Meta names no video-level replacement; its v25.0 notes point to the Media Views and Media Viewers metrics, post_media_view and post_total_media_view_unique, read on the post.
  • Story impressions: STORY_MEDIA_VIEW and STORY_TOTAL_MEDIA_VIEW_UNIQUE.

What changed for Messenger message tags on April 27, 2026?

Requests carrying CONFIRMED_EVENT_UPDATE, ACCOUNT_UPDATE or POST_PURCHASE_UPDATE started failing with error code 100, as Meta's changelog had announced on March 27. HUMAN_AGENT, for a person's reply within 7 days of the customer's last message, was not among them. Meta's routes for the retired uses are utility templates and the Marketing Messages API, and the message tags page sets out what each remaining tag allows.

What else did Meta change for Pages and Messenger in 2026?

Smaller changes, most of them additions, each dated in Meta's changelogs:

  • January 30: the Page Integrity API and webhook report a Page's status, violations, restrictions and appeals.
  • February 11: the Messenger Calling API became generally available to apps with pages_messaging.
  • March 3: appointment booking requests reach the Conversations API and webhooks as appointment_booking attachments.
  • March 6: Messenger utility templates take named parameters, with parameter_format set to NAMED.
  • March 26: post and Reel shares sent in Messenger carry their url, id, type and title.
  • May 19: metadata=1 no longer returns metadata about a node's fields in any version; field lists live in the references.

How do you check an integration against these changes?

Search the code and its request logs for what changed, then run the calls on the version you mean to keep:

  • Version strings below v21.0 in URLs and SDK settings, and the version set in the App Dashboard.
  • date_format, pretty, debug, If-None-Match and GET /?ids= in requests.
  • Retired metric names, such as page_impressions_unique or total_video_impressions.
  • The three retired message tags in Messenger sends.
  • current_location, genre, network, parking and start_info in Page reads.
  • commerce_orders and the other Commerce Order Management endpoints.

How does easyCoexistence handle these changes?

Pages connected to easyCoexistence reach Meta's Graph API through its Meta app, at the Graph API version easyCoexistence sets, which is also the base get_social_credentials returns, so App Review and version moves are handled by easyCoexistence. send_social_dm sends standard replies inside the messaging window, with no message tag, so the April retirement did not touch it, and get_social_insights asks for the metric names your AI passes, so it should pass the replacements above.

Common mistakes

  • Reading only the newest version's changelog. A versioned change lands on the new version first and on older ones later, which is how v26.0's protocol changes reached v25.0 code on October 27, 2026.
  • Keeping date_format for display. Since October 27, 2026 it returns an error in all versions; take Meta's default format and convert it in your own code.
  • Waiting for Meta's date on the legacy Page fields. They already return a version error on v26.0, and Meta has not confirmed when older versions follow, so remove them now.
  • Assuming a removed version fails loudly. Its calls are answered by the next oldest usable version, so code pinned to v20.0 now runs under v21.0's behavior without an error.
Doing this with EasyCoexistence

US$ 9 to US$ 0.75 per connection per month, falling as you add connections, with the first 3 days free.

easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.

Frequently asked questions

What is the latest Facebook Graph API version?

v26.0, released July 29, 2026, with no end date set yet. v25.0, released February 18, 2026, is available until July 29, 2028.

When does Graph API v21.0 stop working?

On January 21, 2027, when Meta deprecates and removes it; calls still pinned to it then go to the next oldest usable version.

Do retired insights metrics return zero or an error?

An error. Meta's API returns an invalid metric error for a deprecated metric in all versions, so the request has to name the replacement instead.

How much does easyCoexistence cost for a Facebook Page?

Each Page is one connection at US$ 9 to US$ 0.75 per connection per month, the price falling as your number of connections grows, and the first 3 days are free.

Keep reading

Connect your first channel in two minutes.

No platform reviews to wait for. Connect WhatsApp, Instagram, TikTok or another channel, then ask your AI to post, reply or report, and watch it work.

  • 3 days free
  • Cancel any time
  • Official APIs only
  • Monitored 24/7

Verified on