Frame.io · Authentication Profile

Frameio Authentication

Authentication

Frame.io secures its APIs with oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode and clientCredentials flow(s).

CompanyMediaVideoCollaborationReview and ApprovalMedia ProductionAdobeContent
Methods: oauth2 Schemes: 2 OAuth flows: authorizationCode, clientCredentials API key in:

Security Schemes

OAuth2 oauth2
· flows: authorizationCode
s2s_auth oauth2
· flows: clientCredentials

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-19'
method: searched
source: openapi/frameio-v4-openapi.json
docs: https://next.developer.frame.io/platform/v4/docs/guides/authentication/overview
note: OAuth2 via Adobe IMS (ims-na1.adobelogin.com). authorizationCode flow for user
  apps (Web/SPA/Native with PKCE), clientCredentials for server-to-server. Legacy
  developer tokens supported via the x-frameio-legacy-token-auth header.
summary:
  types:
  - oauth2
  oauth2_flows:
  - authorizationCode
  - clientCredentials
schemes:
- name: OAuth2
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://ims-na1.adobelogin.com/ims/authorize/v2
    tokenUrl: https://ims-na1.adobelogin.com/ims/token/v3
    scopes: 4
  description: 'For more information, see: https://developer.adobe.com/frameio'
  sources:
  - openapi/frameio-v4-openapi.json
- name: s2s_auth
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://ims-na1.adobelogin.com/ims/token/v3
    scopes: 3
  description: Server to server authentication flow
  sources:
  - openapi/frameio-v4-openapi.json