I can’t create or list webhooks via the V4 API - getting 401 Unauthorized on both GET and POST to `/v4/accounts/{id}/workspaces/{id}/webhooks`.
My OAuth token works fine for other endpoints like `/v4/me` (returns 200), and I’m an Owner with Full Access. Using proper headers with Bearer token and x-adobe-app-id.
The webhook form at developer.frame.io also doesn’t work - team dropdown is empty and submit button does not work.
I’ve verified:
- Token is valid and not expired
- Using correct V4 endpoints
- Account/workspace IDs are correct
- Tried both listing and creating webhooks
Frame.io support redirected me here. Is there special provisioning needed for webhook access? The docs don’t mention any prerequisites or plan requirements (although I have a Pro plan).
I’m building an integration that needs real-time notifications when files are uploaded/updated. Happy to share account details privately with Frame.io staff if needed.
I have consulted the v4 Webhooks page (https://developer.adobe.com/frameio/guides/Webhooks/), but continue to get a 401 unauthorized error. My research implies that my account does not have webhook permissions enabled. Does webhook access require special approval from Frame.io?
Hi @thincdesign FYI the webhook page on developer.frame.io is only for legacy, it does not work with V4. We will have a webhook UI directly in Frame.io via the settings page coming soon.
Can you confirm whether or not you are a content admin on the account you are trying to create a webhook on? I can see that you’ve created 2 webhooks on the same account that you’ve registered with the forums here called FMP FrameIO Webhook, one is active and the other (guessing it was a new one) is not loading for me and would guess there’s an error there with that one. I can see that there are no content admins on your account, only 2 members with yourself being listed as a member, which is probably the problem. Can you go to settings, Users, click on your name or the others you need to have access, and set them as Content Admin on the right hand side instead of Member and try again?
Can you set up postman (or show a terminal output with cURL response) and share what you get when you try to List Workspaces? You will need to GET https://api.frame.io/v4/accounts/:account_id/workspaces/:workspace_id/webhooks
Thanks @CharlieAnderson I seem to have conquered my Webhook problem.
-
I see my user listing identified as an “Admin”, but I don;t see an option anywhere to make myself a “Content Admin”. Can you point me to where that is? I am not confident that I am in the right place.
-
I do have an extra webhooks created that I can delete, but I can not locate a page in v4 land that I can do that. The only Webhooks listing page I find is v2 and nothing is listed there.
-
My next problem is accessing file information with an API call. With the default scopes, I don’t appear to have permissions to access file level information. Is that correct? And how can I change that? I am trying to access the file name.
Many thanks!
hi @thincdesign my apologies, Content Admin is an enterprise feature, so when I saw it on my account I thought it was universal. Can you confirm that you have an Adobe ID connected to your frame.io account under Settings > Profile > Authentication? If you have the Manage on Adobe option that takes you to Adobe Account then you should be okay.
The webhooks on developer.frame.io is only for legacy accounts (V3) and not for V4. We will have Webhooks available on the settings page of V4 once we finish the work on it (hopefully very soon).
401 error means you likely dont have an Adobe ID connected (/4/me will work, but /v4/accounts won’t). Can you try list accounts then list workspaces then list projects then list folder children and let me know what you get returned?
I am connected to my Adobe account…
I’m new to Postman so it is not out of the range of possibilities that I am doing something wrong, but I am getting an error 401 on all of those requests.
Thanks, Charlie!
I suspect that I do not have the Server-to-Server credential set up correctly. Could that be contributing to this problem? I have been unseuccessful in finding any instruction to set that up that actually match my Adobe Admin console. If this is the case, can you point me to the most current instructions? Thanks.
hi @thincdesign S2S is currently enterprise only at this time. Since you have an adobe ID connected to your account I’m going to guess that you are not providing the bearer token correctly in the postman request.
Can you check to make sure your authentication looks like this (for web app user auth).
And then for /v4/accounts:
Thank you so much, @CharlieAnderson, that was it! I had been using the Bearer token authentication.
