Direct HTTP requests reference

Troubleshooting

This topic describes the most common errors and solutions when integrating using direct HTTP requests.

401 Unauthorized when trying to get the browser ID

When trying to retrieve the browser ID, this error occurs when the value for the stream_api_target_endpoint parameter or the value for the client_key parameter is incorrect in the URL.

To fix the error:

For the stream_api_target_endpoint parameter, specify the correct Stream API target endpoint.
For the client_key parameter, specify the correct client key.

400 Bad Request error when trying to send an event

This error occurs when the event object does not contain a browser_id or a type.

To fix the error:

In the HTTP request, in the message query parameter, locate the key-value pairs that describe the event.
For the browser_id key, specify the browser ID that you previously retrieved.
Make sure the event object contains a type.

404 Not Found error when trying to send an event

This error occurs when the event object contains the incorrect browser ID.

To fix the error:

In the HTTP request, in the message query parameter, locate the key-value pairs that describe the event.
For the browser_id key, specify the browser ID that you previously retrieved.

Events not appearing in Sitecore CDP

If you sent an event to Sitecore CDP and the HTTP response has the 201 Created status code, this issue occurs if the value for the pos key is incorrect.

To fix the error:

In the HTTP request, in the message query parameter, locate the key-value pairs that describe the event.
For the pos key, specify the correct name of a point of sale.

If you have suggestions for improving this article, let us know!