401 Error even when I am the owner of the content

Despite being the account owner (as confirmed in the web interface, under Users), I am consistently receiving 401 Not Authorized errors when using the API—particularly when accessing endpoints like /v2/accounts, /v2/accounts/{account_id}/users, and others.
I am certain I am using the correct developer token, generated from the owner account and with the proper account selected in the UI. I have also tried using the OAuth method, still get the same response.

What I Have Tried / Troubleshooting Steps:

  • Confirmed I am logged in as the account owner and have selected “Soch’s Account” at the bottom left of the UI before generating the developer token.
  • Generated multiple new developer tokens to rule out expiry or token context errors.
  • Successfully called /v2/me and confirmed that the token matches the owner account and user IDs.
  • Attempted to call /v2/accounts, /v2/accounts/{account_id}/projects, and /v2/accounts/{account_id}/users with valid tokens and correct IDs.
  • All attempts to access account-level endpoints (such as /users) result in a 401 error, even though I am the listed Owner in the web UI.
  • I have also ensured there are no network or DNS issues—other API endpoints and services work as expected.

Example API response:

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

Request:

  • Please help me resolve this issue, as I need to use the API for automation and integrations as the account owner.
  • If there is an org/account configuration, role, or permission setting I am missing, kindly advise exactly what to change or how to re-enable full API access for the owner.
  • If this is a bug or known limitation with certain plans, please escalate internally and let me know the next steps.

@sochbymm can you confirm whether you are on a V3 (legacy) account or V4? If your account says “Legacy” like in my screenshots here, you are on V3. If it does not say Legacy, then you are on a V4 account and /v2/ routes will not work and you will need to use our V4 API as outlined in our announcement last month.

Screenshot 2025-05-28 at 9.18.18 AM
Screenshot 2025-05-28 at 9.18.23 AM
Screenshot 2025-05-28 at 9.18.48 AM
Screenshot 2025-05-28 at 9.19.08 AM

Thanks for the clarification Charlie. Will confirm to you if the v4 API works for me or not. Cheers :slight_smile:

In the event you recieve 401 errors with the V4 API, that will be likely due to your Frame.io account not being linked to an Adobe ID, in which you will need to reach out to our support team for help (if they are unhelpful, just lmk and I can help as well). We are working on improving that error response to give more details about this very thing.