# /v2/projects/* stops working

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

On December 1, 2026, the endpoint /v2/projects/* will be removed and requests to it will fail. The legacy API will no longer be supported after that date. Any calls targeting /v2/projects/* must be updated before the cutoff.

- 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/projects/*`
- 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-projects-stops-working/

## What to use instead

Call /v4/accounts/{account_id}/projects/{project_id} (GET, PATCH, DELETE) and its V4 sub-resources (collaborators, shares) instead. Switching requires more than changing an identifier, as V4 calls require an Adobe Developer Console project with Adobe IMS OAuth credentials instead of legacy developer tokens or OAuth apps from developer.frame.io.

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.