# /v2/actions/* stops working

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

On December 1, 2026, the Frame.io API will remove V2 API endpoints, causing requests to /v2/actions/* to fail. The legacy API will no longer be supported after that date. Any calls targeting these endpoints will stop working entirely.

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

## What to use instead

Call /v4/accounts/{account_id}/actions/{action_id} for custom actions instead. Moving to V4 requires more than updating an endpoint, as calls require an Adobe Developer Console project with Adobe IMS OAuth credentials, and legacy developer tokens or developer.frame.io OAuth apps will not work.

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.