# /v2/accounts* stops working

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

On December 1, 2026, the /v2/accounts* endpoints will be removed. Calls to these legacy V2 API endpoints will fail after that date as they will no longer be supported.

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

## What to use instead

Call GET /v4/accounts and the account-scoped V4 endpoints under /v4/accounts/{account_id}/ for workspaces, projects, webhooks, and actions. This move requires more than changing an identifier, as V4 calls need an Adobe Developer Console project with Adobe IMS OAuth credentials because legacy developer tokens and OAuth apps from developer.frame.io do not work on V4 accounts.

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.