Comunicate.eu Authentication

generated: '2026-11-04'
method: searched
source: https://comunicate.eu/ro/documentatie-api
summary:
  types:
  - http
  - oauth2
  oauth2_flows:
  - authorizationCode
schemes:
- name: apiKey
  type: http
  scheme: bearer
  description: API key from Integrations (bk_live_…)
  sources:
  - openapi/comunicate-eu-openapi.yml
- name: oauth2
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://app.comunicate.eu/api/v1/oauth/authorize
    tokenUrl: https://app.comunicate.eu/api/v1/oauth/token
    scopes: 10
  description: OAuth 2.1 with PKCE (S256). Dynamic client registration at https://app.comunicate.eu/api/v1/oauth/register.
    The access token is an API key and is accepted everywhere an API key is.
  sources:
  - openapi/comunicate-eu-openapi.yml
docs: https://comunicate.eu/ro/documentatie-api
header: 'Authorization: Bearer bk_live_…'
key_prefix: bk_live_
key_issuance: Keys are issued from the Integrations page and shown once; the provider
  stores only a hash ("se vede o singură dată — noi păstrăm doar amprenta ei, exact
  ca la parole").
unauthenticated_routes: '/public/* routes need no key; in openapi.json they carry
  security: [] and the document has no global security.'
test_keys: 'None documented: only the bk_live_ prefix appears in the docs.'
oauth_docs_note: OAuth 2.1 + PKCE and dynamic client registration are stated in the
  OpenAPI securitySchemes description; the HTML docs page describes only API-key auth.
identity_endpoint: GET /partner/me (operationId get_me) returns the organization,
  the key scopes and the aiPublishing toggle; requires no scope.