Skip to main content
Version: v2

Non-200 Error status codes

note

This is a work in progress, more status codes will be fed here soon.

This doc is intended to help you understand when certain HTTP status codes are thrown when using Browserless. If you're interested in knowing the status code of the site being navigated to by one of our REST APIs, you can find the status code and status in the headers named x-response-code and x-response-status. As far as this doc, we'll be explaining the status code your request returns, but keep in mind that you can get a 200 status code from the request, but a non-200 in the x-response-status.

401 Unauthorized​

This error indicates that the request has not been applied because it lacks valid authentication credentials for the resource.

Troubleshoot:

  • You might not be sending the API key in the WebSocket Endpoint properly
  • Your HTTP Client may be caching an old API key that's no longer valid.
  • You might be using an endpoint not supported by your plan, e.g. trying to use the v2 endpoints, when being on a dedicated or legacy plan.