The Bazaarvoice Displayable Content Export (DCE) provides an HTTP interface for bulk requesting Bazaarvoice Conversations data intended for public display. To learn more, go to the DCE documentation home page.

Contents

(+ show- hide)

The Displayble Content Export (DCE) workflow begins with a request for a manifest file list. Values in the list will be in the form of URL paths which will be used in the next step.

Request

Path

GET https://[stg.]api.bazaarvoice.com/dce/v3/data
Path tokens
Name Description
[stg.]

Optional subdomain indicating the request should use the non-production environment. Omit to use production. Learn more at the Reference section.

Headers

Host: [stg.]api.bazaarvoice.com
X-Bazaarvoice-Passkey: {DCE_PASSKEY}
X-Bazaarvoice-Signature: {SIGNATURE}
X-Bazaarvoice-Timestamp: {TIMESTAMP}

Refer to the Reference section for details on the headers and their values.

Access signature values

Replace the {SIGNATURE} token above with the following string, encrypted using the algorithm described at Creating the Access Signature.

passkey={DCE_PASSKEY}&timestamp={TIMESTAMP}

Replace the tokens above with the appropriate values as described below:

Name Description
{DCE_PASSKEY}

This is the same value communicated with the X-Bazaarvoice-Passkey header.

{TIMESTAMP}

A Unix timestamp in milliseconds. This is the same value communicated by the X-Bazaarvoice-Timestamp header.

Using seconds or any increment other than milliseconds will cause your request to fail

Response

Response will be a JSON object containing URL paths corresponding to available manifests. The following demonstrates a typical response:

{
  "manifests": [
    {
      "version": "v2",
      "fulls": [
        {
          "date": "2017-07-31",
          "path": "/manifests/full/2017-07-31/v2/manifest.json"
        },
        {
          "date": "2017-07-24",
          "path": "/manifests/full/2017-07-24/v2/manifest.json"
        },
        {
          "date": "2017-07-17",
          "path": "/manifests/full/2017-07-17/v2/manifest.json"
        }
      ],
      "incrementals": [
        {
          "date": "2017-07-31",
          "path": "/manifests/incremental/2017-07-31/v2/manifest.json"
        },
        {
          "date": "2017-07-30",
          "path": "/manifests/incremental/2017-07-30/v2/manifest.json"
        },
        {
          "date": "2017-07-28",
          "path": "/manifests/incremental/2017-07-28/v2/manifest.json"
        }
      ]
    }
  ]
}

Full manifests contain all displayable Conversations data and are generated once a week. Use the most recently generated manifest to get a complete snapshot of your Conversations data.

Incremental manifests are generated in response to new and modified content over the previous 24 hour period. The absence of an incremental manifest for a particular period indicates that there is no new or updated content processed during that period.

The URL paths will be used in the next step.