I’ve created an app using adobe developer account for v4 api. Works well as the main user. But if I add a user to my workspace they can’t seem to use the API endpoints. Are they different for added users? It’s like they can’t find the workspace, because for them it doesn’t have the workspace name.
Hi there! Any users of your app will also need to have their Frame and Adobe IDs linked, otherwise Adobe IMS doesn’t have anything to authorize them against. If they’re not linked, they’ll get a 401. We’re working to make this issue a little clearer in the responses, but we recommend accounting for 401 errors for your users by suggesting they may not have their IDs linked and to reach out to support.
Thanks @RobertLoughlin I’m not getting any 401 issues though, I’ve added a user who has an adobe / frameio linked account, and they can use oauth to generate a valid token and query the api. The problem is that the user can’t see the same ‘workspace’, so they can’t actually access the project. They can see the account they’re added to, but it doesn’t list any workspaces. You can even see that in Frameio itself, it just says ‘Invited to’ and doesn’t list any workspaces, and the API can’t seem to access the projects there?
Just to be clear – the user can’t see the workspaces in Frame.io either? Have you added them to the project or to the account? You may have to add them to the workspace directly.
they are added to the workspace. The user can see the project on the actual site. But when they access the api they can return the accounts they’ve been added to but they can’t see the workspace. In Frameio as an added user it doesn’t even show as a workspace, it just says Invited To.
Apologies, I’m having a hard time following the issue the user is having so excuse all my questions. Can you be more specific about how you added them and what exactly you added them to? It sounds like they don’t actually have access to the workspace as a whole, just to the one project.
What is the flow you’re looking to execute for them?
I’ve got a frameio account which is linked to my adobe account, that’s all fine. I’ve made an app using adobe developer, I can generate a token, access the api, which goes to my account, a specific workspace, and a specific project. That all works fine. I’ve then set up a new account to test adding users. That account is also linked to an adobe account, and I’ve added that user to the workspace. Again that’s all fine. That user can also generate a token and use it to access the api. That user can access / see the original account too. But there are no workspaces when they access via the api. I don’t think ‘workspaces’ exist for shared users? How can someone other than the original account and workspace owner access the project via the api?
@WikRik did you invite this person to a project? aka does it look like this in the UI?
If so, then the API does not return any workspaces or projects you are Invited to at this time. It is on the roadmap to solve for. You need to be added as a member of the workspace to access it via the API
ah man thank you, that was such a subtle difference. I’d added them, but didn’t realise you also then have to specifically add them to the workspace. I think I’d added them to the account and also to the project. Wow, phew thank you, api access now working.