Adobe org missing Frame.io product entitlement - Team plan, matching Adobe ID linked as workspace member, following topic 3304

Help
1

Hi Frame io Developer team,

Sent here from Technical Support (Jayshree Bharti) who confirmed this needs Developer team assistance. Same underlying issue as topic 3304 (Umanity), which Rosie Cunningham resolved via DM on 28 May 2026.

Setup (confirmed):

  • Frame io Team plan, ~136 projects, in daily production use since 2020+.
  • Team log in with a shared account owner login (deliberately not linked to any Adobe ID).
  • A separate Adobe ID exists, is linked to Adobe, and is already a member of the Frame. ioworkspace. Amisha (Technical Support) confirmed via chat that this satisfies the “matching email between Adobe ID and Frame io member” rule.
  • Adobe Developer Console project sits under that linked Adobe ID, configured with an OAuth Web App credential and the Frame io API added.

The gap:

The Adobe org backing the Developer Console project shows only Acrobat PDF Services API as an entitled product. Frame io is not provisioned. Adobe IMS returns {"error":"access_denied"} on grant_type=refresh_token. Charlie Anderson noted in prior threads that “API entitlements are tied to contracts / sales” — that’s the gate we’re hitting.

Adobe Admin Console displays the banner: “We have detected that your organization is no longer entitled to the following APIs and services that were added to this project - Frame io API.”

Historical:

Same setup was working end March through April 2026 via a Zapier Custom Action (upload.to.vimeo) → Vimeo pull upload. Stopped firing to Vimeo around May, coinciding with what looks like an Adobe grace-period rollback. The Zap itself still fires end to end but returns early because Adobe IMS rejects the token exchange.

Ask:

Provision Frame io as an entitled product on the Adobe org backing our Developer Console project, same treatment Rosie extended to Umanity in topic 3304.

Constraint:

The Frame io account owner login is deliberately not linked to any Adobe ID and needs to stay that way (team continues to sign into Frame io the way they always have). The Adobe linkage lives entirely on a separate workspace-member Adobe ID and should stay there.

Happy to share the account owner email, linked Adobe ID email, Adobe Org ID, Client ID, workspace UUID, and request/response logs via DM whenever you need them. Thanks.

2

Hi @eiau

Happy to help here. One thing to note is that in order to use the V4 API, you need a Frame./io account linked to an Adobe ID. This is a requirement, and there isn’t a workaround for that.

That said, I just sent over a message requesting some information so I can take a look at your accounts on my end, and should be able to provide some next steps with respect to that.