Copy page

Frame.io V4

Twin of the Frame.io V4 API.

Twin of the Frame.io V4 API, not the older V2 one, and a V4 token does not work on V2.

Covers	api.frame.io
Auth	Adobe IMS bearer tokens
Webhooks	No
Operations	23

Coverage

The signed-in user and the accounts they own, workspaces, the project and folder tree, and webhook registration. Files and uploads, comments, shares, users and groups, metadata and search sit outside this twin: a call to one answers 501 in Frame.io’s own error envelope rather than returning a plausible empty result.

Credentials

This twin issues no tokens of its own. It verifies the ones Adobe IMS mints, so any well-formed V4 bearer token from there authenticates by default and your existing credentials need no change. The auth.mode switch that restricts it to credentials the world knows lives on Adobe IMS rather than here. See Credentials. A revoked token stops working immediately.

Vendor specific details

• Validation runs before the lookup, so a badly shaped id is a 422 and not a 404. Every violation in the request comes back at once, not just the first.
• Webhook registrations are stored and read back, but nothing is ever delivered. The V4 OAuth grant carries no webhook scope, so a real integration could not authorize delivery either. Do not build a test that waits for one.
• An account you do not own is a 401, but a folder or webhook belonging to another account addressed through your own account URL is a 404.
• The links.next URL drops page_size, so a paged walk quietly falls back to the default page size unless you put it back on every request.

Its own notes

Once a sandbox is running, this twin serves its own operating notes at {control_url}/veris/manual: the credentials it accepts, the API versions it serves, and the fault statuses you can arm against it. They are generated from the same source as its behaviour, so they cannot drift.