V2 token cannot access Marketing Examined workspace; Gmail account cannot use Adobe/V4 OAuth

General
1

Hi Frame.io team,

I’m trying to get API access for the Marketing Examined workspace so our internal system can import a specific folder, 2026 HoD Projects.

The complication: my Frame.io workspace admin access is tied to my Gmail/Google-authenticated Frame.io account, not my Adobe ID. I cannot disable Gmail login or switch the account to Adobe auth without risking access to the workspace, so the V4 OAuth path is currently blocked for me.

The workspace/project URL I need to access is:

Using my V2 developer token:

GET /v2/me -> 200, returns my user
GET /v2/accounts -> []
GET /v2/teams -> []
GET /v2/accounts/{account_id}/teams -> []
GET /v2/projects/PROJECT_ID -> 404
GET /v2/assets/ASSET_ID-> 403
Search /v2/search/assets?q=2026&type=folder -> []

I am a workspace admin in the Frame.io UI, so I’m confused why the V2 token cannot see any accounts, teams, projects, or folders.

I found a couple of similar forum threads where V2 returns empty teams/404 projects even for admins/account owners, and another where V4 workspaces return empty when users have multiple account profiles. This seems related to account profile/auth identity rather than normal workspace permissions.

Can someone confirm the correct path here?

  1. Can a Gmail/Google-authenticated Frame.io admin use the V4 API without disabling Gmail login or converting the login to Adobe ID?
  2. Can Frame.io link my existing Gmail-authenticated Frame.io admin user to Adobe auth without breaking workspace access?
  3. If Marketing Examined is V4-only, is there any V2 fallback token or legacy folder ID that can access its folders?
  4. If this is caused by multiple account profiles, can Frame.io support check whether my user/token is attached to the wrong profile for API access?

Goal: list the Marketing Examined workspace, projects, root folders, and folder children so we can import only the 2026 HoD Projects folder.

Thanks,
John

2

Hi @kaufmann42!

Your Frame.io account needs to be connected to your Adobe account. This is something that our support team can help sort out pretty quickly for you. This will require temporarily deactivating Google Auth on your account, but this can be reinstated once the accounts are linked.

Here is a link you can use to get in touch: Frame.io | Contact Us

If you continue to run into any issues with this after your accounts have been linked, please follow up here so we can help troubleshoot further.

Also just a quick heads up: I edited your original post to swap out the asset and project IDs with placeholders.