Bloom · OAuth Scopes

Bloom OAuth Scopes

OAuth 2.0 searched

Bloom publishes 2 OAuth 2.0 scopes via the authorizationCode, clientCredentials, and refreshToken flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Bloom API on a user’s behalf.

Tokens are issued from https://www.trybloom.ai/api/auth/oauth2/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyBrand ManagementImage GenerationArtificial IntelligenceAgentsMCPMarketingCreative

Scopes: 2 Flows: authorizationCode, clientCredentials, refreshToken Method: searched

OAuth endpoints

Authorization URL
https://www.trybloom.ai/api/auth/oauth2/authorize

Token URL
https://www.trybloom.ai/api/auth/oauth2/token

Flows
authorizationCodeclientCredentialsrefreshToken

Scopes (2)

Scope	Description	Flows
openid	OpenID Connect identity scope (advertised in scopes_supported).	authorizationCode
offline_access	Issue a refresh token for long-lived access (advertised in scopes_supported).	authorizationCode

📄 Provider scope reference: https://www.trybloom.ai/docs/api/authentication

Source

OAuth Scopes

generated: '2026-07-21'
method: searched
source: >-
  https://www.trybloom.ai/.well-known/oauth-authorization-server (RFC 8414
  metadata, saved verbatim at well-known/trybloom-oauth-authorization-server.json)
  and https://www.trybloom.ai/docs/api/authentication.md. The OpenAPI declares
  apiKey/bearer schemes only, so the scope surface comes from the published
  OAuth metadata rather than the spec.
docs: https://www.trybloom.ai/docs/api/authentication
notes: >-
  Bloom OAuth is identity-scoped rather than permission-scoped: access tokens
  resolve to the same user identity as an API key, with the same access to
  brands, images, credits, plan gates, and workspaces. Public clients use
  Authorization Code + PKCE (S256) with dynamic client registration (RFC 7591)
  and no client_secret; wildcard redirect URIs are not supported.
schemes:
  - name: Bloom OAuth
    issuer: https://www.trybloom.ai/api/auth
    flows:
      - flow: authorizationCode
        authorizationUrl: https://www.trybloom.ai/api/auth/oauth2/authorize
        tokenUrl: https://www.trybloom.ai/api/auth/oauth2/token
        pkce: S256 required for public clients
      - flow: clientCredentials
        tokenUrl: https://www.trybloom.ai/api/auth/oauth2/token
      - flow: refreshToken
        tokenUrl: https://www.trybloom.ai/api/auth/oauth2/token
    registration: https://www.trybloom.ai/api/auth/oauth2/register
    jwks: https://www.trybloom.ai/api/auth/jwks
    introspection: https://www.trybloom.ai/api/auth/oauth2/introspect
    revocation: https://www.trybloom.ai/api/auth/oauth2/revoke
    userinfo: https://www.trybloom.ai/api/auth/oauth2/userinfo
scopes:
  - scope: openid
    description: OpenID Connect identity scope (advertised in scopes_supported).
    flows: [authorizationCode]
    sources: [well-known/trybloom-oauth-authorization-server.json]
  - scope: offline_access
    description: Issue a refresh token for long-lived access (advertised in scopes_supported).
    flows: [authorizationCode]
    sources: [well-known/trybloom-oauth-authorization-server.json]