# /v2/hooks/* stops working

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

On December 1, 2026, the Frame.io legacy API endpoints at /v2/hooks/* will be removed and will fail. Calls to these legacy V2 routes will no longer be supported after that date.

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

## What to use instead

Call /v4/accounts/{account_id}/webhooks/{webhook_id} with GET, PATCH, or DELETE instead. Moving requires more than changing an identifier, as V4 calls need an Adobe Developer Console project with Adobe IMS OAuth credentials rather than legacy developer tokens or 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.