generated: '2026-07-18'
method: searched
source: openapi/bazaarvoice-content-search-openapi.json
docs: https://developers.bazaarvoice.com/v1.0-ConversationsAPI/docs/api-key-management
summary:
  types:
  - apiKey
  - oauth2
  api_key_in:
  - header
  - query
  oauth2_flows:
  - clientCredentials
  note: >-
    Bazaarvoice uses two authentication models across its API surface. The Conversations
    and Content Search APIs authenticate with an API passkey (the Bv-Passkey header in
    the V2.0 Content Search API, or the Passkey query parameter in the classic
    Conversations API). Passkeys are requested and managed in the Bazaarvoice Portal's
    API Key Management application and must be activated by a Technical Administrator.
    The Transactions API and Response API instead use 2-legged OAuth2 (client
    credentials) and do not accept passkeys.
schemes:
- name: Bv-Passkey
  type: apiKey
  in: header
  parameter: Bv-Passkey
  description: >-
    API passkey for the Content Search API, sent as the Bv-Passkey request header.
    Requested and managed in the Bazaarvoice Portal API Key Management application.
  sources:
  - openapi/bazaarvoice-content-search-openapi.json
- name: Passkey
  type: apiKey
  in: query
  parameter: passkey
  description: >-
    API passkey for the classic Conversations API, supplied as the Passkey query
    parameter (e.g. ?ApiVersion=5.4&Passkey={apikey}).
  docs: https://developers.bazaarvoice.com/v1.0-ConversationsAPI/docs/api-key-management
- name: OAuth2ClientCredentials
  type: oauth2
  flow: clientCredentials
  tokenUrl: https://developers.bazaarvoice.com/v1.0-TransactionsAPI/reference/post_auth-v1-oauth2-token
  description: >-
    2-legged OAuth2 (client credentials) for the Transactions API and Response API.
    client_id and client_secret are issued by Bazaarvoice Support; a token is obtained
    from the POST /auth-v1/oauth2/token endpoint. No passkey is used for these APIs.
  docs: https://developers.bazaarvoice.com/v1.0-TransactionsAPI/docs/oauth2-2-legged