V4 API returns empty workspaces array - account owner, free tier

Help
,
1

Hi,

I’m hitting the same issue as several other threads - GET /v4/accounts/{account_id}/workspaces returns an empty array even though I’m the account owner and can see my workspace, project, folders and assets normally in the Frameio UI.

My setup:

  • Free tier V4 account, Adobe-connected
  • I am the account owner (not an invited member)
  • I have a workspace with a project, folder and assets, all visible and working in next.frame.io

What works:

  • 3-legged OAuth flow through Adobe IMS (ims-na1.adobelogin.com) completes successfully
  • Scopes granted: openid, AdobeID, offline_access, email, profile, additional_info.roles
  • GET /v4/accounts returns my account correctly with a valid account ID
  • The account ID is a valid UUID and is passed correctly in the request path

What fails:

  • GET /v4/accounts/{account_id}/workspaces → {"data":[],"links":{"next":null}}
  • Because workspaces is empty, I can’t get a workspace_id to call the projects endpoint

What I’ve verified:

  • The account ID is correct (pulled directly from /v4/accounts, not hardcoded)
  • The token is valid and not expired (other authenticated endpoints work)
  • I’m using the exact documented endpoint paths
  • I’ve reconnected/re-authorised multiple times with full scopes
  • This is my own account that I own, so it shouldn’t be an “invited to workspace but not added to account” situation

From the other threads it looks like this gets resolved by a staff member adding the user properly to the account on the backend. Could you please DM me so I can share my account details privately and get this sorted?

Tagging @CharlieAnderson and @rosiec as you’ve both helped resolve this exact issue before.

Thank you!

2

hi @Dan can you give this endpoint a try and see if it works for you?

please note it’s in Experimental atm and requires the api-version:experimental in the header request.

3

Thanks @CharlieAnderson! that experimental endpoint works and does return data. But it surfaced a deeper issue. I ran a diagnostic hitting four endpoints and here’s what I get:

  • GET /accounts/{id}/projects (experimental) → returns only ONE project, which is a project shared with me from another user’s workspace (restricted: true, workspace_id: a1ef3f4d-...)
  • GET /accounts/{id}/invited_projects (experimental) → returns the same shared project, confirming it’s an invited one
  • GET /accounts/{id}/workspaces → empty {"data":[]}
  • per-workspace projects → nothing, since workspaces is empty

The problem: my own project doesn’t appear in any endpoint. I own a project called “daniel’s first project” that lives in my own workspace. But my workspaces list comes back empty, and my own project shows up in neither the by-account nor the invited list. The only thing the API can see is a project invited to me from someone else’s workspace.

This looks like my own account/workspace isn’t fully provisioned on the backend — the same class of issue as the older “workspaces returns null” threads. Could you take a look on your end? Happy to share any other details via DM.

Thanks again!

Dan

4

Hi Dan,

What you’re describing usually happens when you have multiple account profiles associated with your user. When you have a moment, can you shoot me a direct message containing the email address you’re using to log in?

5

Thanks @rosiec - sorry for the cluelessness, but how do I send you a DM?