General Troubleshooting Steps

Perform the following steps to troubleshoot a DCE issue.

Check that the credentials (passkey and secret) are correct.
Look for typos in the protocol, domain, URL and path.
Ensure that you are using the correct headers.
Verify the access signature was created correctly:
- Access signature values should match the corresponding values used elsewhere in the request.
- Access signature values are different for each request. Make sure you are using the correct values.
Check the table below for error specific tips.
Contact us for assistance.

Error Specific Troubleshooting Tips

🚧
The errors below refer to the latest version of the DCE HTTP Service. Refer to the reference section for previous version errors.

The following table shows common errors along with tips to help you troubleshoot.

Response	Troubleshooting
No Response	Verify domain is correct.
401 Unauthorized	Request must include `X-Bazaarvoice-Signature` and `X-Bazaarvoice-Timestamp`. Headers are present but values are invalid. Verify that all values used in creation of signature are correct. Access token must not be expired. Tokens are valid for 300 seconds after creation of timestamp.
403 Forbidden	Request must include `X-Bazaarvoice-Passkey.` Wrong passkey or passkey not approved yet. Key / environment mismatch. EX: staging key used with production domain. If you're getting 403 response from S3 when your code following redirect, please split request in two – first retrieve S3 redirect location from BV API and then create a new request without Host header to perform GET from S3.
404 Not Found	Path incorrect. EX: missing `/data`.
5XX Errors	Try again in a few minutes. If the error is not resolved, contact us for assistance.

Still having trouble? Contact us for assistance.