I’ve been trying to authenticate to the Frame v4 API and I’m having no success. I’ve been following the excellent documentation here:
https://developer.adobe.com/frameio/guides/
I have an application in the developer console, have a Webapp credential, and have both the API Collection and Environment loaded into Postman. I am able to successfully get access tokens and generate new tokens with the refresh token.
However I am not able to use the token for the v4 Frame API to successfully get my user info from the API. When I try to hit the /v4/me endpoint, I get either 401 Unauthorized or 403 Forbidden depending on what I have selected for the Token Type.
If I have Access token selected in the Authorization tab for the API, I get 401 Unauthorized.
If I have ID token selected in the Authorization tab for the API, I get 403 Forbidden.
I’m not sure what else to try, thanks for any help you can provide.
JasonW
Hey Jason the /v4/me endpoint you’re targeting is currently being re-worked which is why you’re having issues.
There’s a work-around we can help you out with but I’m going to follow-up on the email thread that we already have going with some other folks at Chesa to get you looped in and we can go from there!
1 Like
Hi Jeff,
Sorry to bug, but I haven’t heard anything yet on our side for that workaround you mentioned.
I think I managed to find my account ID using the dev tools in my browser to examine the graphql, but that’s as far as I’ve gotten and hitting other endpoints like /v4/accounts/:account_id/workspaces I still get 401.
I have a call with the customer we’re on the hook to do work for this on Thursday, I’d just like to give them a status update if possible.
Thanks for your time!
jw
I am having the same issue on my end using v4 api, kindly guide any helpful solution for above issue, or when its expected to fix
my bad i have entered invalid scopes.
Having the same issue when trying to get /me with a valid token obtained using the Postman oauth workflow. Any ideas?
You most likely haven’t linked your frame.io user to your Adobe identity.
There isn’t yet a way to self-serve this identity linking, but we’re working on it!
We’re also working on improvements to the API response in the event you end up in this state so that it’s easier to debug and resolve, that should ship in the next one to three weeks.
In the meantime, if you reach out to our support team and ask for help linking your Frame.io user to your Adobe identity so that you can access the API they should be able to help!
