# /v2/comments/* stops working

Calls to /v2/comments/* on Frame.io API stop working on December 1, 2026.

On December 1, 2026, the /v2/comments/* endpoints will be removed. Calls to these routes will fail after that date as the legacy V2 API endpoints lose support.

- API: Frame.io API (api.frame.io)
- Kind: Endpoint removal
- Announced: June 18, 2026
- Takes effect: December 1, 2026
- Calls after that day: fail
- Calls it hits: `/v2/comments/*`
- Source: [Announcement](https://forum.frame.io/t/v4-api-migration-questions-discussion/3368)
- Page: https://www.okapi.bot/providers/frame-io-api/breaking-changes/v2-comments-stops-working/

## What to use instead

Migrate by calling /v4/accounts/{account_id}/comments/{comment_id} for GET, PATCH, and DELETE operations. Moving to V4 requires more than an endpoint update, as calls require an Adobe Developer Console project with Adobe IMS OAuth credentials instead of legacy developer tokens or developer.frame.io OAuth apps.

V4 calls need an Adobe Developer Console project with Adobe IMS OAuth credentials: legacy developer tokens and OAuth apps from developer.frame.io do not work on V4 accounts.

## Frame.io API's words

> The Frame.io legacy API is being deprecated and will no longer be supported after December 1, 2026. After that date, V2 API endpoints will be removed.