Bloomreach · OAuth Scopes

Bloomreach OAuth Scopes

OAuth 2.0 probed

Bloomreach publishes 3 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Bloomreach API on a user’s behalf.

Tokens are issued from https://us.connect.loomi.ai/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.

Digital CommerceSearchMerchandisingRecommendationsCustomer Data PlatformCDPEmail MarketingSMS MarketingMarketing AutomationHeadless CMSPersonalizationE-Commerce

Scopes: 3 Flows: authorizationCode Method: probed

OAuth endpoints

Authorization URL
https://us.connect.loomi.ai/authorize

Token URL
https://us.connect.loomi.ai/token

Flows
authorizationCode

Scopes (3)

Scope	Description	Flows
openid	Standard OIDC scope — issue an ID token for the signed-in Bloomreach user.	authorizationCode
profile	Standard OIDC scope — basic profile claims for the signed-in Bloomreach user.	authorizationCode
email	Standard OIDC scope — email claim for the signed-in Bloomreach user.	authorizationCode

📄 Provider scope reference: https://documentation.bloomreach.com/loomi-connect/docs/authenticate-mcp-connection

Source

OAuth Scopes

generated: '2026-08-13'
method: probed
source: https://us.connect.loomi.ai/.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource/mcp
docs: https://documentation.bloomreach.com/loomi-connect/docs/authenticate-mcp-connection
description: The only OAuth surface Bloomreach publishes is the Loomi Connect MCP authorization server.
  None of the product REST APIs uses OAuth — Engagement is Token/Basic, Content is an opaque x-auth-token,
  Discovery is account_id + auth_key — so there is no REST scope surface to derive. Effective authorization
  on the MCP server is carried by Bloomreach IAM roles, not by OAuth scopes.
schemes:
- name: Loomi Connect MCP OAuth
  source: well-known/bloomreach-loomi-oauth-authorization-server.json
  issuer: https://us.connect.loomi.ai/
  flows:
  - flow: authorizationCode
    authorizationUrl: https://us.connect.loomi.ai/authorize
    tokenUrl: https://us.connect.loomi.ai/token
    registrationUrl: https://us.connect.loomi.ai/register
    pkce: S256
    refresh: true
    client_auth:
    - client_secret_post
    - client_secret_basic
scopes:
- scope: openid
  description: Standard OIDC scope — issue an ID token for the signed-in Bloomreach user.
  flows:
  - authorizationCode
  sources:
  - well-known/bloomreach-loomi-oauth-authorization-server.json
- scope: profile
  description: Standard OIDC scope — basic profile claims for the signed-in Bloomreach user.
  flows:
  - authorizationCode
  sources:
  - well-known/bloomreach-loomi-oauth-authorization-server.json
- scope: email
  description: Standard OIDC scope — email claim for the signed-in Bloomreach user.
  flows:
  - authorizationCode
  sources:
  - well-known/bloomreach-loomi-oauth-authorization-server.json
authorization_model:
  note: The three scopes above are identity scopes only — they grant no product permission. What the agent
    may actually read or write is decided by the caller's existing Bloomreach IAM role on each project,
    enforced server-side. Callers without administration.pii.flag receive PII masked to ****** and cannot
    override it from the tool.
  iam_docs: https://documentation.bloomreach.com/data-hub/docs/unified-administration#role-management-by-product
other_oauth_surfaces:
- issuer: https://www.bloomreach.com/en
  scopes_supported:
  - mcp
  source: well-known/bloomreach-oauth-authorization-server.json
  note: An RFC 8414 document served by the WordPress marketing website advertising a single "mcp" scope.
    It is not an API product surface.

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/bloomreach-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.