Bloomberg Data Workflows OAuth Scopes

OAuth 2.0 probed

Bloomberg Data Workflows uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

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.

Enterprise DataFinancial AnalyticsFinancial-ServicesInvestment ManagementMarket DataReference DataTrading

Scopes: 0 Flows: authorization_code, refresh_token Method: probed

Scopes (0)

Bloomberg Data Workflows implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

No public scopes/permissions reference page exists for any Bloomberg API. This artifact is probed from the live discovery document, not searched from documentation.

📄 Provider scope reference: https://www.bloomberg.com/.well-known/oauth-authorization-server

Source

OAuth Scopes

generated: '2026-08-27'
method: probed
source: https://www.bloomberg.com/.well-known/openid-configuration
docs: https://www.bloomberg.com/.well-known/oauth-authorization-server
description: >-
  The only OAuth scope surface Bloomberg publishes anonymously is the bloomberg.com identity
  provider's discovery document. Scopes were read verbatim from `scopes_supported`; no scope
  descriptions are published, so the descriptions below state only what the scope name and the
  surrounding discovery metadata establish, and are marked as such. The Data License REST API
  (api.bloomberg.com/eap) uses per-request signed JWTs rather than OAuth scopes and therefore
  contributes no scopes; BLPAPI/SAPI uses Terminal entitlements, not scopes.
schemes:
  - name: bloomberg-com-oidc
    type: openIdConnect
    source: https://www.bloomberg.com/.well-known/openid-configuration
    issuer: https://www.bloomberg.com
    authorization_url: https://login.bloomberg.com/api/oauth/authorize
    token_url: https://login.bloomberg.com/api/oauth/token
    flows: [authorization_code, refresh_token]
    pkce_required_methods: [S256]
scopes:
  - name: openid
    scheme: bloomberg-com-oidc
    description: >-
      Standard OpenID Connect scope; requests an ID token for the authenticated Bloomberg account.
    description_source: OIDC Core 1.0 (the provider publishes no scope description)
  - name: user
    scheme: bloomberg-com-oidc
    description: >-
      Access to the authenticated user's Bloomberg.com profile. Bloomberg publishes no description
      or claim list for this scope.
    description_source: inferred-from-name
  - name: entitlements
    scheme: bloomberg-com-oidc
    description: >-
      Access to the authenticated user's Bloomberg subscription entitlements. Bloomberg publishes
      no description or claim list for this scope.
    description_source: inferred-from-name
scope_count: 3
note: >-
  No public scopes/permissions reference page exists for any Bloomberg API. This artifact is
  probed from the live discovery document, not searched from documentation.

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/bloomberg-data-workflows-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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