Request: Enable v4 Resource Scopes

Help
1

Hi team,

I’ve linked my Frame.io account to my Adobe ID and created an OAuth Web App in the Adobe Developer Console, with the Frame.io API added.

Currently, I only have the default scopes (profile, offline_access, email, additional_info.roles, openid) and so far all /v4 endpoint calls return 401 Unauthorized.

Forum discussions suggest the issue is missing server-enabled resource scopes such as:

asset:read
project:read
asset:comment.read

(and possibly transcript:read)

These are not editable in the Console, so could you please enable the necessary resource scopes for my app?

I’m aiming to automate the export of asset data, metadata, and custom fields into an Excel/CSV sheet using Make.com. Let me know if you need any details.

Thanks,
Marlon

2

Hi Marlon!

profile, offline_access, email, additional_info.roles, openid are the only scopes you need for the V4 API. The other scopes you have listed here are exclusive to the V2 Legacy API.

There are a few things to check:

  • Make sure your test user has access to a V4 account, workspace, and project
  • Double check that your IDs are actually linked.
    • If you get sent to the Adobe login page when logging in, the link was successful.
    • If it was not successful, try logging out of Frame.io and logging back in.
    • If it’s still not successful, let me know and I can reset the linking process on the backend.

Are you getting a 401 in your app or in a testing environment like Postman?

3

Hi @marlon like Rob said, 401 errors are typically associated with a user not having an Adobe ID linked to their Frame.io account. You can find more information about how to solve that here.