Frame.io API · Endpoint removal
/v2/hooks/* stops working
Stops working (in 39 days)
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.
What to use instead of these calls
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.
Calls it hits
/v2/hooks/*
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.
Facts
- API
- Frame.io API
api.frame.io - Kind
- Endpoint removal
- Announced
- June 18, 2026
- Takes effect
- December 1, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
More from Frame.io API
- /v2/accounts* stops working Stops working
- /v2/actions/* stops working Stops working
- /v2/assets/{} stops working Stops working
- /v2/assets/{}/* stops working Stops working
- /v2/comments/* stops working Stops working
- /v2/projects/* stops working Stops working