← Home

How to run the V2 → V4 route map

Use this page when Frame.io removes V2 API endpoints on 2026-12-01 and you still have clients calling /v2, legacy team resources, or mixed Camera to Cloud (C2C) traffic. The home tool stays in your browser; it never calls Frame.io or Adobe APIs. Always re-check the official V2 deprecation notice and Adobe Frame.io migration guides before you treat a ticket as done.

  1. Confirm the official V2 removal date and migration guides. Open the Frame.io V2 API deprecation notice and Adobe developer Frame.io Migration guides. Note 2026-12-01 and which resources rename under V4. Do not rely only on this static site.
  2. Inventory every client that still calls /v2. Search repos, gateways, Zapier-like glue, and device logs for api.frame.io/v2 or legacy host paths. Record owner, path patterns, and auth style (legacy token vs Adobe OAuth).
  3. Separate C2C device calls from general API clients. C2C traffic is often on an exempt fork—do not blindly rewrite those paths until official notes say they must move. Mark C2C vs non-C2C on the home tool.
  4. Paste leftover /v2 paths into the home route map. Include teams, assets, and related resources you still hit. Wrong pastes produce the wrong rewrite hints.
  5. Build the map and copy Markdown. Click Build, then Copy Markdown into the migration ticket. Keep Dec 1 in the title so route work is not buried under unrelated Adobe IMS chores.
  6. Rewrite non-C2C clients to V4 bases and resource names. Move /v2 → /v4 (per current Adobe base paths), map teams → workspaces, and remap assets toward files / folders / version_stacks as the official map dictates. Update SDKs and hand-rolled HTTP clients together.
  7. Plan Adobe OAuth / legacy token cutover. Clients still on legacy tokens need an Adobe IMS / OAuth plan and any required legacy headers during transition. Document secrets rotation outside this page—never paste tokens here.
  8. Verify and audit close-out. Hit staging with rewritten routes; confirm C2C devices still follow the exempt path if applicable; attach the exported map plus deprecation URLs; calendar Dec 1 even if some services already speak V4.

Related: FAQ · Use cases · Home tool. Sources: Frame.io V2 API deprecation notice, Adobe Frame.io Migration guides, Frame.io community V4 migration threads.