# /v2/assets/{} stops working

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

On December 1, 2026, the /v2/assets/{} endpoint will be removed as part of the legacy Frame.io API deprecation. Requests made to this endpoint after that date will fail.

- 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/

## What to use instead

Assets map to files, folders, and version stacks in V4, so call /v4/accounts/{account_id}/files/{file_id} or /v4/accounts/{account_id}/folders/{folder_id} instead. Migrating requires more than updating endpoints, as V4 calls require 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.