Im trying to use the V4 api for frame.io, the support helped me link frame.io to my Adobe ID and I’m able to create access tokens through my client id and secret. But any request I send gets a 401. Ive tried the /me and /accounts endpoints and both give me 401. Ive made sure I’m using the following scopes; openid profile offline_access additional_info.roles in postman and I’ve even made a new project in adobe to get new oauth2 details but still the same thing.
The weird part is, my other account works perfectly fine. Its linked to a different adobe account and that one works for some reason, while on this account it doesn’t. Someone help me out please I’m losing it lol
Hi there! Are your two Adobe accounts two separate IDs (ie, two different email addresses) or are they two different profiles on the same ID? We can only link your Frame ID with one Adobe ID. If you’re using two different Adobe IDs, this could be why you’re seeing a 401 on one (the unlinked ID) and not the other (the linked ID).
Thanks – so to be clear, you have two different Frame IDs as well, and there’s no overlap? Feel free to email me those two IDs and I can take a look on the backend to see if there are any identity issues. API access for Frame.io managed accounts is still in early access, so we’re ironing out the kinks in the management side of things. Thanks!
@RobertLoughlin@CharlieAnderson@jhodges having a similar issue but my Frame.io and Adobe entity have already been linked and work “properly”. The process seems that the oauth does not refresh the token automatically and therefore after x amount of time, it will start giving unauthorized errors. The only way it will work again, is if we recreate the oauth entirely. I’m using Make.com Oauth 2.0 module for reference.
@bell My guess would be you haven’t configured the OAuth 2.0 module correctly to support token refresh. You definitely shouldn’t have to recreate the OAuth config entirely every time though.
Approximately how long is “x amount of time”? The auth token you get initially should be valid for 24 hours, after which you can use the refresh token to get a new auth token for 14 days - but partway through those 14 days, the refresh token is replaced by a new one, which you would then use going forwards.
Yes I believe 24h is exactly the time it’s doing it now - the oauth itself is configured correctly I’d say, it authenticates just fine right away with no errors (normally if either of the inputs are wrong it won’t let you continue). How else can I test if that’s the cause?
@jhodges I just tried re-setting up the oauth to send you a screenshot to confirm, there’s definitely something going on with the API keys, the key that worked fine on the first connection now tells me invalid client. I had to create an entire new project to reset it and it works (at least on the first oauth, the refresh token will probably fail).
Sending you a DM also of the setup just to confirm it’s the proper way to do it - if you could take a look that would be great!