Linking existing self-serve Frame.io Team account to Adobe organization for V4 API access — entitlement missing in Adobe Admin Console

Help
1

Hi Frame.io team and community,

Looking for guidance on connecting an existing self-serve Frame.io Team plan account to my company’s Adobe organization so V4 API calls can authorize successfully. Frame.io support directed me here.

My situation:

  • I have a Frame.io Team plan account set up directly through Frame.io (not via an Adobe-managed migration). I use it daily for review/approval workflows.
  • I have a separate Adobe organization (dezi-capsulemedia.tv) where I created an Adobe Developer Console project with an OAuth Web App credential for the Frame.io API per your V4 documentation.
  • Adobe IMS auth works cleanly: refresh-token grants succeed, access tokens mint, scopes are correct (openid,profile,additional_info.roles,offline_access, omitting email per the v4-403 landmine).

The problem:

Every V4 endpoint returns a generic edge HTTP 403 (“403 Forbidden” HTML, no Frame.io app body), including read-only endpoints like /v4/me. The bare-edge response (no Frame.io app body) suggests rejection at the API gateway before reaching app logic.

My diagnosis:

In Adobe Admin Console, my dezi-capsulemedia.tv org has only one product entitlement listed: Acrobat Services: PDF Services API. Frame.io is not listed as an entitled product on this Adobe org. Per @CharlieAnderson’s note in the OAuth 401/403 thread — “API entitlements are tied to contracts / sales” — that appears to be the cause. Without Frame.io as an entitled product on this Adobe org, the API gateway has no contract-level reason to authorize this org’s bearers.

I read help article 10552820 on Adobe-managed Frame migration, which describes a top-down Adobe-scheduled migration process — not a self-serve link operation.

My questions:

  1. Is there a self-serve path to link my existing Team plan account to my Adobe org’s product list? Or is this strictly Adobe-scheduled?

  2. If self-serve linking isn’t possible on Team plan, what’s the path forward? Tier upgrade? New Frame.io account creation under the Adobe org? A specific migration request flow to Adobe?

  3. For Make.com / Zapier users on Team plan whose V4 API access works: are those connectors using a different OAuth client (Make’s / Zapier’s own pre-registered Frame.io app with their own contract-level entitlement)? If so, is there documentation on creating a similar pre-registered app for n8n self-hosted, OR a supported flow where I authorize Make.com / Zapier’s pre-registered app and proxy through their platform?

  4. Are there any non-API automation paths officially supported by Frame.io for Team plan? I’m aware of:

    • Frame.io desktop app’s transfer features (does it support headless / scripted upload from a watch folder?)
    • Adobe Premiere panel (works but not headless)
    • C2C protocol (camera-to-cloud, not applicable to my server-side use case)

    Anything else worth evaluating for headless server-side automation?

Stack details:

  • Self-hosted n8n on Railway (Debian-based custom image, n8n@1.123.38)
  • Adobe Developer Console project: Umanity Agents — Frame.io User Auth (project ID 4193752)
  • Use case: production AI content agency uploading rendered video assets for client review/approval workflows, scaling to 25–100 spots per client per month

Frame.io is the preferred review/approval portal for our workflow — Drive doesn’t fit this use case for us. Drive may end up as a fallback for final asset delivery, but the review/feedback layer needs to live in Frame.io. Looking for ANY path that gets rendered video assets into a Frame.io workspace headless / scripted, ideally without manual UI interaction.

Happy to share captured request/response logs via DM if needed.

Thanks for the help.