Frame.io V4 API: 401 Not Authorized when accessing /v2/me using Adobe IMS OAuth Token

Help
,
1

Hi Frame.io Dev Team,

We are setting up an automated integration to upload files from Dropbox to Frame.io V4 for our studio account. Since legacy developer tokens are disabled for our account (“This account does not allow legacy developer tokens”), we followed the recommended route:

  1. Created a dedicated automation user linked to Adobe ID with access to our Frame.io workspace.

  2. Created an OAuth Web App project in Adobe Developer Console with the Frame.io API added.

  3. Successfully completed the OAuth authorization flow (/ims/authorize/v2 → /ims/token/v2).

The Issue:

Adobe IMS returns a valid access token (200 OK), but any request to [https://api.frame.io/v2/me](https://api.frame.io/v2/me) or /v2/projects/{project_id} using Authorization: Bearer <access_token> and x-api-key: <client_id> returns:

JSON

{
  "code": 401,
  "message": "Not Authorized",
  "errors": [{ "code": 401, "status": 401, "title": "Not Authorized", "detail": "You are not allowed to access that resource" }]
}

Could you please check if an API entitlement / feature flag needs to be enabled for our Account ID or Client ID to allow Adobe IMS OAuth access to Frame.io V4 resources?

Thank you!

2

Hi @RAMbiota!

All the /v2 endpoints are for the legacy API, make sure you’re calling against the V4 API endpoints, which you can see here: User details | Frame.io API Documentation

For example, the new endpoint for me is /v4/me.

3

Hi @RAMbiota!

Thanks for letting us know about this, sorry to hear you’re running into some trouble here.

First thing to call out is that you are referencing Legacy API routes in your post. Specifically, api.frame.io/v2/me and /v2/projects/{project_id}

The current versions of those endpoints are:

  • /v4/me (docs here)
  • /v4/accounts/:account_id/workspaces/:workspace_id/projects (docs here)

This Quick Start guide has a breakdown of how to get started, along with the endpoints you can use to verify your auth setup: Quick Start | Frame.io API Documentation

Also, just in case you haven’t seen it, the troubleshooter in this post walks through the most common causes for 401 errors, so it is a good place to start if you’re still stuck after walking through the Quick Start: 401 Error? Start here!

(Also, just a heads up, I edited your original post to remove your email address and account ID.)