Meta Graph API versions: the newest version and every end date

The newest Graph API version documented on this site is v26.0, which Meta released on July 29, 2026 together with Marketing API v26.0. The next end date coming up is v21.0, which Meta's version table lists as available until January 21, 2027.

This page covers the Graph API versions documented in our API changelog, with the dates Meta gives for each. If Meta has released a version after v26.0, it isn't on this page yet: the changelog lists the newest entries first.

What this means for you

The Graph API is how apps, such as schedulers and reporting tools, connect to Facebook Pages and Instagram professional accounts. Meta numbers each version, and each one gets an "available until" date. When that date passes, a tool still using that version is past what Meta says is available.

Most people never pick a version: the tool you post with does that for you. The dates matter if you rely on a small or home-made tool, or if your Facebook and Instagram reports suddenly show gaps.

Every Graph API version and its end date

Every date comes from Meta's version table or release posts, as recorded in the linked entry. Where our entry doesn't give a date, the table says so instead of guessing. The version table itself doesn't describe what happens to a request after a version's end date, so treat each date as the deadline to move.

What changed in each recent version

v26.0, July 29, 2026. It removes the Commerce Order Management API with no replacement, and it blocks several legacy Page fields (current_location, genre, network, parking, start_info) for New Pages Experience pages. On the ads side it retires the Instagram Explore placement and poll ad creation.

The same release removed older request features. Meta now ignores the pretty and debug parameters, returns a parameter error for date_format and for root GET /?ids= requests, and drops ETag and If-None-Match caching. That applied to v26.0 calls from July 29, 2026 and to all remaining versions from October 27, 2026. Details: legacy request features removed.

v25.0, February 18, 2026. From March 31, 2026, the Webhooks mTLS client certificate is signed by a Meta-owned CA instead of DigiCert, while the common name stays client.webhooks.fbclientcerts.com. Receivers that check the certificate must trust meta-outbound-api-ca-2025-12.pem. The metadata=1 parameter was deprecated and removed on all versions on May 19, 2026.

v25.0 also announced the removal of reach metrics such as page_impressions_unique and post_impressions_unique. Meta's own sources disagree on when: the v25.0 blog post says June 2026, the v25.0 changelog ties it to the v26.0 release. See Page and post reach metrics deprecated.

v24.0, October 8, 2025. It removes the Certificate Transparency endpoints and webhooks, for all versions from October 17, 2025, and the overlay_url field on live videos.

v23.0, May 29, 2025. Mostly ads changes, such as Advantage+ audience defaults, and instagram_destination_id now returns ig_user_id. Its changelog lists no Pages, permissions or webhook changes.

v22.0, January 21, 2025. It deprecates Facebook Page recommendations (error code 12 for v22.0 and later), the Instagram impressions and plays metrics in favour of views, and the Instagram v1.0 API. The Instagram side has its own timeline in Instagram API versions: what replaced v1 and Basic Display.

What to do next

• Business owners: Nothing to change yourself. If someone built a script or small app that posts to your Facebook Page or Instagram account, ask which Graph API version it calls. v21.0 or older needs moving before January 21, 2027.
• Marketers and agencies: If Facebook impressions or reach vanished from a client report, check the dates: Meta deprecated impressions and page fans on November 15, 2025, then reach with v25.0. Ask the reporting tool whether it uses the views metrics, such as page_total_media_view_unique.
• Developers: Search your code and config for v21.0 and older, test against a newer version, and upgrade. Remove pretty, debug, date_format, root /?ids= reads and ETag caching if you still send them, and trust Meta's new CA if you verify webhook certificates.

Everything else that changed for Meta publishing is on the Facebook hub and the Instagram hub.