← Home

FAQ

What breaks if clients still call /v2 after 2026-12-01?

Frame.io’s deprecation path removes V2 endpoints. Callers that keep /v2 bases risk hard failures on teams, assets, and related resources. Treat Dec 1 as a hard cut for non-exempt clients, then verify against the live deprecation notice rather than tribal memory.

Why is teams → workspaces called out separately from the base path?

A naive host rewrite to /v4 still fails when code assumes legacy teams resources. V4 expects workspaces (and related file/folder/version_stack shapes). The home map forces both base and resource renames into the ticket so path-only PRs do not strand resource IDs.

Are Camera to Cloud (C2C) device calls exempt?

Often yes per official notes—but exemptions are not a blanket forever pass for every integration. Mark C2C explicitly on the tool, read the current deprecation language, and keep device firmware owners in the loop. Blindly rewriting C2C the same way as media-collab app traffic is a common footgun.

Do legacy tokens still work through the V4 migrate?

Plan on Adobe OAuth / IMS for modern clients. Legacy tokens may need transitional headers or outright replacement. This site never collects tokens; your ticket should name the auth owner and rotation steps beside the route map.

Can I finish OAuth work and skip rewriting /v2 routes?

No. Auth without route/resource rewrites still fails when V2 is removed. Route rewrites without auth readiness still fail at handshake. Answer both “leftover /v2” and auth/C2C prompts so the pack ranks them together.

Does this replace Frame.io / Adobe developer consoles or call the API for me?

No. This is a local api-route-rewrite checklist and Markdown exporter. It does not mutate projects, rotate Adobe credentials, or scrape accounts.

Where should I verify dates before closing the ticket?

Frame.io updates V2 API deprecation notice and Adobe developer Frame.io Migration guides. If those pages move a date or resource map, they win over any copy on this site.

Is this official Frame.io or Adobe documentation?

No. Unofficial local helper. Not affiliated with Frame.io or Adobe.

Do you store my answers or tokens?

No. Pasted paths stay in the browser session; Copy Markdown uses the clipboard API only. We never ask for OAuth secrets or device keys.