# /v2/teams/* stops working

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

On December 1, 2026, the /v2/teams/* endpoints will be removed as part of deprecating the legacy API. Calls to /v2/teams/* will fail after this date. The endpoints will no longer be supported once the removal takes effect.

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

## What to use instead

Teams are workspaces in V4, so call /v4/accounts/{account_id}/workspaces/{workspace_id} and access projects under /v4/accounts/{account_id}/workspaces/{workspace_id}/projects. Moving requires more than updating paths: 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.