Bloomberg AIM · Authentication Profile

Bloomberg Aim Authentication

Authentication

Bloomberg AIM secures its APIs with http and oauth2 across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

Financial DataMarket DataOrder ManagementPortfolio ManagementTrading
Methods: http, oauth2 Schemes: 3 OAuth flows: clientCredentials API key in:

Security Schemes

bearerAuth http
scheme: bearer
oauth2 oauth2
· flows: clientCredentials
basicAuth http
scheme: basic

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/bloomberg-data-license-api.yml, openapi/bloomberg-emsx-api.yml, openapi/bloomberg-http-api.yml
summary:
  types:
  - http
  - oauth2
  oauth2_flows:
  - clientCredentials
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: Bloomberg-issued JWT credential obtained from the Bloomberg Console.
  sources:
  - openapi/bloomberg-data-license-api.yml
  - openapi/bloomberg-emsx-api.yml
- name: oauth2
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://bsso.blpprofessional.com/ext/api/as/token.oauth2
    scopes: 3
  description: OAuth 2.0 client credentials flow
  sources:
  - openapi/bloomberg-data-license-api.yml
- name: basicAuth
  type: http
  scheme: basic
  description: HTTP Basic authentication for the local API server
  sources:
  - openapi/bloomberg-http-api.yml