# /v2/assets/{}/* stops working

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

On December 1, 2026, the legacy API endpoint /v2/assets/{}/* will be removed and will no longer be supported. Calls to this endpoint will fail after that day. The deprecation was announced on June 18, 2026, as part of the phase-out of V2 API endpoints.

- 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/assets/{}/*`
- 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-assets-stops-working-2/

## What to use instead

Call the V4 folder and file endpoints: /v4/accounts/{account_id}/folders/{folder_id}/children, /files/{file_id}/comments, copy, move and version stacks under /v4/accounts/{account_id}/. Moving requires more than updating endpoints, as V4 calls need an Adobe Developer Console project with Adobe IMS OAuth credentials instead of legacy developer tokens and 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.