--- updatedAt: 2026-03-30T09:25:15.000Z agentTools: projectIndex: https://developers.bazaarvoice.com/v1.0-PS-Export/llms.txt --- # 2. Request Manifest File Location In this step you will request the location of a manifest file that contains a listing of all data sets available from the Product Sentiment Export. The response to this request will be a 302 redirect to the location of the manifest file. ## Request ### Path ```http GET https://[stg.]api.bazaarvoice.com/psi/v1/data?path={MANIFEST_PATH} ``` #### Path tokens [block:html] { "html": "\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n

Name Description

Name	Description
`[stg.]`	Optional subdomain indicating the request should use the non-production environment. Omit to use production. In either case, production data will be returned. Learn more at the Reference section.
`{MANIFEST_PATH}`	\n This is a file path acquired from the previous step. \n ⚠ The file path must be used exactly as it is. Any modification will result in an error. \n

[stg.]

Optional subdomain indicating the request should use the non-production environment. Omit to use production. In either case, production data will be returned. Learn more at the Reference section.

{MANIFEST_PATH}

This is a file path acquired from the previous step.

⚠ The file path must be used exactly as it is. Any modification will result in an error.

" } [/block] ### Headers ```http Host: [stg.]api.bazaarvoice.com X-Bazaarvoice-Passkey: {PSI_PASSKEY} X-Bazaarvoice-Signature: {SIGNATURE} X-Bazaarvoice-Timestamp: {TIMESTAMP} ``` Refer to the [Reference](/v1.0-PS-Export/docs/http-service-v1) section for details on the headers and their values. #### Access signature values Replace the `{SIGNATURE}` token above with the encrypted string generated using the algorithm described in the "[Creating the Access Signature](/v1.0-PS-Export/docs/creating-access-signature)" section. ```http path={MANIFEST_PATH}&passkey={PSI_PASSKEY}×tamp={TIMESTAMP} ``` Replace the tokens above with the appropriate values as described below: [block:html] { "html": "\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n

Name Description

Name	Description
`{MANIFEST_PATH}`	This is a file path acquired from the previous step. This is the same value communicated in the `path` query string parameter.
`{PSI_PASSKEY}`	This is the same value communicated with the `X-Bazaarvoice-Passkey` header.
`{TIMESTAMP}`	\n A Unix timestamp in milliseconds. This is the same value communicated by the `X-Bazaarvoice-Timestamp` header. \n ⚠ Using seconds or any increment other than milliseconds will cause your request to fail \n

{MANIFEST_PATH}

This is a file path acquired from the previous step. This is the same value communicated in the path query string parameter.

{PSI_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

" } [/block] ## Response Response will be a HTTP 302 redirect to the location of the manifest file. The response will also include the location path value in the body of the request as a convenience for applications that cannot be configured to follow the redirect automatically. The following demonstrates a typical response: ```http HTTP/1.1 302 Found Content-Type: application/json Location: {MANIFEST_URL} {"location":"{MANIFEST_URL}"} ``` Some headers have been removed for clarity. The next step will describe how your application can use the location path value to request a manifest file.