Hi everyone,
I’m running into a persistent issue with the Frame.io API and hoping to get some clarity. I’ll attach screenshots as well.
Summary of the Issue
Whenever I try to fetch an asset using the Frame.io API at:
GET https://api.frame.io/v2/assets/{asset_id}
I receive the following error:
404 Not Found
"detail": "Could not find the requested resource"
This happens even though:
-
The asset definitely exists (I receive its ID via a webhook event).
-
I’m the account owner, biller, and workspace/project owner.
-
I’m using a Developer Token generated from the Developer Console.
-
The token includes full scopes (
asset.read,project.read,team.read,webhook.read, etc.). -
I’ve tested the request in Postman, curl, Make.com, and the result is always the same.
-
The webhook event I receive from Frame.io includes:
resource.id = (some-uuid)
resource.type = file
project.id = (project uuid)
workspace.id = (workspace uuid)
Despite this, the API still returns a 404 when requesting /v2/assets/{resource.id}.
Context: Using the New Frame.io V4 UI
My account is using the new V4 UI, which I understand is part of Adobe’s updated Frame.io infrastructure.
I’m trying to confirm whether:
1. My plan/workspace has API access at all
– Are V2 API endpoints still supported for users on the V4 interface?
– Is API access limited only to Enterprise / V4 API customers now?
2. The Webhook resource.id in V4 is no longer the actual asset ID
The webhook payload uses:
type: metadata.value.updated
resource.type: file
resource.id: (uuid)
Is this ID not supposed to be used with /v2/assets/{id} under V4?
If so, what is the correct way (or endpoint) to retrieve the actual asset when using V4 webhooks?
3. Or if this is an account-level configuration issue
Is there something wrong with my workspace/project’s API access configuration?
Again — I’m the owner, biller, and creator of all workspaces and projects in my account.