Custom OAuth works, but Developer Console says organization is no longer entitled to Frame.io API

Help
,
1

Hi Frame.io team — I’m requesting diagnosis/provisioning for custom V4 OAuth user authentication on an existing Frame-managed V4 account.

Account and project

  • Frame.io account: KoreanAmericanStory.org
  • Frame.io account ID: REDACTED
  • Current plan: legacy Pro
  • Operator is an active Content Admin; Frame.io Profile → Authentication shows Manage on Adobe, so the Frame.io and Adobe identities are already linked
  • Adobe Developer Console organization: hi-ingwon.io
  • OAuth Web App client ID: 015a98f837f649109dd35bebaa9ad4a0 (public identifier only)

We are not requesting Server-to-Server credentials. We only need three-legged OAuth user authentication, which Frame.io staff have said is not tied to a specific plan level.

What works

  • The Adobe Developer Console project has Frame.io API connected to an OAuth Web App, the expected localhost redirect, and the operator in its beta-user list.
  • Authorization-code exchange succeeds.
  • Refresh-token exchange succeeds and issues a valid one-hour access token.
  • The first-party Frame.io API explorer’s List Accounts request returns HTTP 200 for the same user and lists KoreanAmericanStory.org with an admin role.

What fails

With the access token issued to our custom OAuth client:

  • GET https://api.frame.io/v4/me → plain HTML HTTP 403
  • GET https://api.frame.io/v4/accounts → plain HTML HTTP 403

The Adobe Developer Console project also displays this warning:

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.

We re-consented with the documented identity scopes and also tested after removing the email scope, per prior forum guidance. Token issuance still succeeds and the Frame.io API still returns 403.

Request

Could the Frame.io team please:

  1. restore/provision the custom V4 API entitlement for this Adobe organization/project, or
  2. advise which Adobe organization/profile must own the OAuth project for this already-linked Frame-managed account?

This is an internal integration for KAS media inventory and temporary benchmark upload/list/cleanup operations, not an external SaaS application. I can provide the Adobe ID email, request IDs, and redacted logs by direct message. I will not post client secrets, refresh tokens, or access tokens publicly.

Thank you.

2

hi @aboynamedcrow thanks for your post, lets see if we can help.

First, I redacted your account_id from your post (please don’t put sensitive information on public forums, DM someone on the frame team if you need to supply that information).

Second, can you try to remove the Frame.io API from your developer console project and re-add it and try again? Or create a new project in the developer console with a new frame.io API added to it (which will have a new client_id & secret).

Are you using our SDKs that include auth modules in them or are you using your own cURL commands? The fact that the explore works but your custom OAuth does not is interesting (and that even /me 403s when that should work regardless as it hits IMS).

The developer console message is most likely why there’s a 403 but curious as to what could be the cause here.

If you’re using a LLM you can add our docs mcp to your agent of choice if that’s helpful:
https://next.developer.frame.io/_mcp/server