Frame.io V4 API - Adobe IMS returns "invalid_scope" - Which scopes to use?

1

Hi everyone,

Following up on my previous post about V4 API 401 errors, I’ve made progress debugging but hit a new blocker.

Context: I’m building a SaaS that integrates with Frame io V4 API. My Frame io account is linked to Adobe ID and I can access Frame io web app normally via Adobe authentication.

Current issue: Adobe IMS returns invalid_scope error during OAuth, before I even get a token:

https://ims-na1.adobelogin.com/ims/authorize/v2?
  client_id=xxx&
  scope=openid&
  redirect_uri=xxx

→ Callback: error=invalid_scope

What I’ve tried:

Scope Result
openid invalid_scope
openid,offline_access invalid_scope
openid email profile offline_access invalid_scope

Every combination fails with the same error.

My Adobe Developer Console setup:

  • Project created with Frame io API added :white_check_mark:

  • OAuth Web App credentials configured :white_check_mark:

  • Redirect URI working :white_check_mark:

The problem: Only generic Adobe scopes are visible in my console: openid, email, profile, offline_access, additional_info.roles

I don’t see any Frame.io-specific scopes.

Questions:

  1. What scopes should I request for Frame io V4 API?

  2. Are there Frame.io-specific scopes that should appear in Adobe Developer Console?

  3. Is V4 API still in Early Access with restricted access?

  4. Has anyone successfully authenticated to V4 API via Adobe IMS? What scopes did you use?

Thanks for any help!

Mathieu

2

Hey Mathieu!

Glad to hear you were able to get the 401 errors sorted. V4 API access is not restricted. Here are the scopes to include in your request to ims/authorize/v2:

offline_access, openid, email, profile, additional_info.roles

Hope this helps!