Bloomberg Applications · OAuth Scopes
Bloomberg Applications OAuth Scopes
OAuth 2.0
searched
Bloomberg Applications publishes 3 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the Bloomberg Applications API on a user’s behalf.
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 APIFinancial AnalyticsFinancial ServicesMarket DataReal-Time Data
Scopes: 3
Flows:
Method: searched
Scopes (3)
| Scope | Description | Flows |
|---|---|---|
| openid | Standard OpenID Connect scope. Requests an id_token identifying the bloomberg.com account. Signed RS256; keys at the published jwks_uri. | |
| user | Access to the authenticated user's bloomberg.com profile. Bloomberg publishes the scope name in discovery but no claim-level reference page; description is limited to what the discovery document states. | |
| entitlements | Access to the account's Bloomberg product entitlements. This is the scope that matters for API consumers: Bloomberg's authorization model is entitlement-driven end to end, and the same concept appears in BLPAPI as EMRS entitlements and NOT_ENTITLED_FIELD errors. |
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.