Bazaarvoice

Bazaarvoice is a leading customer experience platform that helps brands collect, display, and analyze user-generated content including reviews, ratings, and Q&A to build trust and drive sales through authentic customer insights.

Power end-to-end data operations for your Bazaarvoice API with Nexla. Our bi-directional Bazaarvoice connector is purpose-built for Bazaarvoice, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Bazaarvoice or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Bazaarvoice workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Bazaarvoice credential in Nexla, you need to obtain your DCE passkey and HMAC shared secret from your Bazaarvoice account. Bazaarvoice uses HMAC (Hash-based Message Authentication Code) authentication for secure API access to the Displayable Content Export (DCE) API, using a passkey and shared secret to create HMAC signatures for API requests.

1. Access Bazaarvoice Developer Portal: Sign in to your Bazaarvoice Developer Portal or contact your Bazaarvoice account representative to request DCE API access.

2. Obtain DCE Credentials: Request or retrieve your DCE credentials from Bazaarvoice:

   • DCE Passkey: A unique identifier used in HMAC signature creation
   • DCE HMAC Shared Secret: A secret key used to generate HMAC signatures for API authentication

3. Identify API Environment: Determine which Bazaarvoice API environment you want to use:

   • Production: https://api.bazaarvoice.com - Used when your application is complete. Contains consumer-generated content from real end-users.
   • Staging: https://stg.api.bazaarvoice.com - Used while developing your application. Contains test data, not from real end-users.

4. Review HMAC Signature Requirements: Understand how HMAC signatures are created for Bazaarvoice API requests. The signature is generated using your passkey, shared secret, and request parameters. For detailed instructions, see the Bazaarvoice DCE Creating Access Signature documentation.

5. Copy Credentials: Copy your DCE passkey and HMAC shared secret immediately after receiving them. Keep these credentials secure, as they provide access to your Bazaarvoice DCE data.

   Bazaarvoice DCE credentials provide programmatic access to your Bazaarvoice content data. Keep your DCE passkey and HMAC shared secret secure and do not share them publicly or commit them to version control systems. The credentials are used to create HMAC signatures that authenticate API requests. The HMAC signature is included in request headers (X-Bazaarvoice-Passkey, X-Bazaarvoice-Signature, X-Bazaarvoice-Timestamp). For detailed information about Bazaarvoice DCE authentication and HMAC signature creation, see the Bazaarvoice DCE documentation.

For additional information about Bazaarvoice DCE API authentication and credential management, see the Bazaarvoice Displayable Content Export documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Base Url	Yes	No	Your Bazaarvoice DCE Environment API Allowed values: Production: https://api.bazaarvoice.com (Used when your application is complete. The data in production is consumer generated content submitted by real end-users.); Staging: https://stg.api.bazaarvoice.com (Used while developing your application. The data is not derived from real end users.)
DCE Passkey	Yes	Yes	Your DCE passkey for creating HMAC signature. See https://developer.bazaarvoice.com/displayable-content-export/tutorials/creating-access-signature for instructions.
DCE HMAC Shared Secret	Yes	Yes	Your DCE shared secret for creating HMAC signature. See https://developer.bazaarvoice.com/displayable-content-export/tutorials/creating-access-signature for instructions.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Bazaarvoice

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Select the API base URL from the API Base Url dropdown menu. This determines which Bazaarvoice API environment you want to use:

   • Production: https://api.bazaarvoice.com - Used when your application is complete. The data in production is consumer-generated content submitted by real end-users.
   • Staging: https://stg.api.bazaarvoice.com - Used while developing your application. The data is not derived from real end users.
   The API base URL determines which Bazaarvoice environment you're accessing. Use staging for development and testing, and production for live applications. The base URL is used to construct all API endpoint URLs for your requests.

4. Enter your Bazaarvoice DCE passkey in the DCE Passkey field. This should be the passkey obtained from your Bazaarvoice account. The passkey is used together with the shared secret to create HMAC signatures for API authentication.

5. Enter your Bazaarvoice DCE HMAC shared secret in the DCE HMAC Shared Secret field. This should be the shared secret obtained from your Bazaarvoice account. The shared secret is used together with the passkey to generate HMAC signatures for API requests.

   The DCE passkey and HMAC shared secret are used to create HMAC signatures for Bazaarvoice API requests. The HMAC signature is automatically generated by Nexla using your credentials and request parameters. The signature is included in request headers (X-Bazaarvoice-Passkey, X-Bazaarvoice-Signature, X-Bazaarvoice-Timestamp) for all API requests. Keep your credentials secure and do not share them publicly or commit them to version control systems. For detailed information about HMAC signature creation, see the Bazaarvoice DCE Creating Access Signature documentation.

6. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Bazaarvoice connector tile, then select the credential that will be used to connect to the Bazaarvoice instance, and click Next; or, create a new Bazaarvoice credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Bazaarvoice endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get Manifest File List

This endpoint retrieves the DCE manifest file list from your Bazaarvoice account. The manifest file list contains information about available data files, including product data, review data, and other content types. Use this endpoint when you need to see what data files are available for download.

• This endpoint automatically retrieves the manifest file list. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses GET requests to the Bazaarvoice DCE API endpoint ({base_url}/dce/v3/data). The endpoint URL is automatically constructed based on your credential's API base URL configuration.
• The endpoint will return the manifest file list containing information about available data files. The response data is returned at the root level of the JSON response ($), containing manifest information, file paths, and metadata about available data sets.
• The endpoint does not use pagination and returns the complete manifest file list in a single request.

This endpoint retrieves the manifest file list, which is the first step in the Bazaarvoice DCE workflow. The manifest contains information about available data files, including full and incremental data sets. The endpoint requires HMAC authentication, which is handled automatically by your credential configuration. The HMAC signature is included in request headers (X-Bazaarvoice-Passkey, X-Bazaarvoice-Signature, X-Bazaarvoice-Timestamp). For detailed information about the manifest file list and DCE workflow, see the Bazaarvoice DCE documentation.

Get Products

This endpoint retrieves product data from your Bazaarvoice account using a multi-step process. The endpoint first fetches the manifest file list, then retrieves the product manifest file, and finally downloads the product data files. Use this endpoint when you need to access complete product data including reviews, ratings, and other product information.

• Select the DCE data set type from the DCE data set type dropdown menu. Available options are:

  • incrementals: Retrieves incremental data sets containing only changes since the last export (default)
  • fulls: Retrieves full data sets containing all available data

• The endpoint uses a multi-step process to retrieve product data:

  • Step 1: Fetches the manifest file list from {base_url}/dce/v3/data
  • Step 2: Retrieves the product manifest file path from the manifest list based on the selected data set type
  • Step 3: Downloads the product data files from the paths specified in the product manifest
• The endpoint automatically handles the multi-step workflow, chaining API calls to fetch the manifest, locate product files, and download product data. The endpoint uses file-based iteration for the final step to process product data files.
• The endpoint will return all product data from the selected data set type. Product data includes product information, reviews, ratings, and other product-related content. The response data is extracted from product files, with each product record processed individually.
• The endpoint uses file-based pagination for the final step, automatically processing multiple product data files as needed.

This endpoint uses a multi-step workflow to retrieve product data. The endpoint first fetches the manifest file list, then locates the product manifest file based on the selected data set type (fulls or incrementals), and finally downloads and processes product data files. The endpoint requires HMAC authentication, which is handled automatically by your credential configuration. The endpoint uses file-based iteration (iteration.type: body.as.file) for the final step to process product data files. For detailed information about the DCE workflow and product data retrieval, see the Bazaarvoice DCE documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Bazaarvoice data sources can also be manually configured to ingest data from any valid Bazaarvoice DCE API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, path to data, metadata, and request headers.

Bazaarvoice DCE API endpoints follow the pattern {base_url}/dce/v3/{api_path}, where {base_url} is your API base URL (e.g., https://api.bazaarvoice.com) and {api_path} is the specific API path (e.g., /data for the manifest, /data?path={file_path} for data files). The HMAC signature headers (X-Bazaarvoice-Passkey, X-Bazaarvoice-Signature, X-Bazaarvoice-Timestamp) are added automatically from your credential configuration and do not need to be set manually.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Bazaarvoice data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.