Skip to content
Start in the sandboxStart free
All connectors
Frame.io logo

Frame.io

Content creation & media

Move briefs, assets and sign-offs through Frame.io without chasing between tools.

22 ways to read, 3 ways to write, each write switched on by you.

Try this in the sandboxBring us a workflow

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Frame.io with Nexra

Connected, approved, proven.

The things teams do most with Frame.io, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Comment on a fileApproval by rule
  • Upload file (local, multi-part)Approval by rule
  • List accountsRead

Example flow

  1. Frame.io · List accountsDone
  2. Frame.io · Comment on a fileNeeds approval
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Frame.io.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Frame.io
  • Frame.io's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

Frame.io V4 accounts, workspaces, projects, folders, files, version stacks, metadata, comments and review links, plus comments, remote (URL) uploads and local (multi-part) uploads.

Adobe API docs
Source actions
22
Destination actions
3
Data types
17

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

Accounts1
  • List accountsSource

    Frame.io accounts the authorised user belongs to, with roles and storage.

Assets1
  • Search the accountSource

    Searches files, folders, version stacks and projects by name and content.

Comments3
  • Comment on a fileDestinationNot retried automaticallyApproval before production

    Adds a comment to a file, optionally at a frame (video) or page (PDF).

  • Get commentSource

    One comment, optionally with replies.

  • List file commentsSource

    Comments on a file, optionally with replies and owner display names.

File metadata1
  • Get file metadataSource

    Metadata field values (system and custom fields) for one file.

File upload status1
  • Get file upload statusSource

    Whether a file's upload (including a remote upload) has completed or failed.

Files2
  • Get fileSource

    One file with status, size, media type and (optionally) metadata.

  • List files in a folderSource

    Files directly inside a folder, with status, size and media type.

Folder children1
  • List folder contentsSource

    Files, folders and version stacks directly inside a folder.

Folders2
  • Get folderSource

    One folder.

  • List subfoldersSource

    Folders directly inside a folder (use a project's rootFolderId to start).

Local uploads1
  • Upload file (local, multi-part)DestinationNot retried automaticallyApproval before production

    Creates a file in a folder and uploads its bytes to the pre-signed part URLs Frame.io returns.

Metadata fields1
  • List metadata field definitionsSource

    Account-level metadata (custom) field definitions.

Projects2
  • Get projectSource

    One project, including its root folder ID.

  • List projectsSource

    Projects in one workspace, or every project in the account when no workspace is given.

Remote uploads1
  • Upload file from URLDestinationNot retried automaticallyApproval before production

    Creates a file in a folder that Frame.io fetches from an HTTPS URL (remote upload).

Share assets1
  • List review link assetsSource

    Assets included in a share (review link).

Shares2
  • Get review linkSource

    One share (review link). Read only.

  • List review linksSource

    Shares (review links) on a project, with access, expiry and permissions. Read only.

Version stack versions1
  • List versions in a stackSource

    The files (versions) inside a version stack.

Version stacks2
  • Get version stackSource

    One version stack with its head version.

  • List version stacks in a folderSource

    Version stacks directly inside a folder, with the head version.

Workspaces2
  • Get workspaceSource

    One workspace.

  • List workspacesSource

    Workspaces in the account.

Access and limits

Authentication
Adobe IMS OAuth client and refresh token
Plans and access
Frame.io V4 accounts administered through the Adobe Admin Console, or Frame-managed accounts switched to Adobe authentication. Requires an OAuth Web App credential for the Frame.io API in the Adobe Developer Console. Results are limited to what the authorising user can see.
Test environment
Frame.io has no sandbox. Use a test workspace or project; remote uploads consume account storage.
Rate limits
Frame.io uses leaky-bucket limits per account user and endpoint, documented in the OpenAPI file: most reads and comments 100 calls per minute; file, folder and version-stack listings and remote uploads 5 calls per second; file details 10 per second. HTTP 429 is retried with backoff (Retry-After when present).
Pagination
Cursor pagination: page_size up to 100 (default 50); links.next carries an opaque after cursor. Single-direction only.
Provider events
Frame.io V4 supports workspace webhooks (file, comment, review and share events). Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Never deletes files, folders, version stacks, projects, workspaces, comments, shares or webhooks, and never moves, copies or renames assets.
  • Review links (shares) are read only: creating shares, changing their access or adding reviewers is not offered, so Nexra never opens assets to public viewing. Share passphrases are never mapped.
  • Remote uploads ask Frame.io to fetch a file from an HTTPS URL. Local uploads (local_uploads.create) send a file Nexra holds or fetched, up to 2 GiB, to the pre-signed part URLs Frame.io returns, without credentials and with x-amz-acl: private. Poll file_upload_status.get afterwards. Part URLs are accepted only on Amazon S3 Transfer Acceleration hosts (*.s3-accelerate.amazonaws.com, as Frame.io's upload guide shows); Frame.io's production bucket name could not be confirmed, so a part URL elsewhere fails the upload before any bytes are sent.
  • Media-link downloads and comment attachments are not offered.
  • User e-mail addresses (creators, comment authors, reviewers) are never mapped; only user IDs and display names. Share reviewers and user-role lists are not offered.
  • There is no updatedSince filter. Sort listings by updated_at descending where the endpoint allows.
  • Legacy developer tokens (x-frameio-legacy-token-auth) and server-to-server credentials are not supported; use an OAuth Web App credential.
  • Workspace, project, folder and metadata-field writes, custom actions and webhook management are not offered.

Developer reference

  1. Create the Adobe credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Frame.io, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Adobe docsAPI referenceAdobe docsAuthenticationAdobe docsRate limitsAdobe docsWebhooks

Machine-readable detail: GET /api/public/connect/connectors/frame-io and the Connections API.