# GET /v2/me stops working

Calls to GET /v2/me on Frame.io API stop working on December 1, 2026.

On December 1, 2026, the GET /v2/me endpoint will be removed and calls to it will fail. The legacy API is being deprecated and will no longer be supported after that date. Requests made to this endpoint will not function once it is shut down.

## What to use instead

Call GET /v4/me instead. Moving requires more than updating the endpoint, as V4 calls require an Adobe Developer Console project with Adobe IMS OAuth credentials because legacy developer tokens and OAuth apps from developer.frame.io do not work on V4 accounts.

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.

- 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: `GET /v2/me`
- Source: [Announcement](https://forum.frame.io/t/v4-api-migration-questions-discussion/3368)
- Verified: November 6, 2026, against Frame.io API's own pages
- Page: https://www.okapi.bot/providers/frame-io-api/breaking-changes/get-v2-me-stops-working/

## 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.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent