Table of contents

1. Common Errors and Their Identification in GeoScraper API
   1. 401 Status Code
      1. Berserker Token Missing
   2. 400 Status Code
      1. Invalid Requests
   3. 404 Status Code
      1. End of the Results!

Common Errors and Their Identification in GeoScraper API

When using the GeoScraper API, you may encounter various errors. Understanding these common errors and their causes can help you troubleshoot issues more effectively.

401 Status Code

Berserker Token Missing

• This error is returned when the X-Berserker-Token is not included in the request header.
• Action: Ensure that you include a valid X-Berserker-Token in your request headers.

400 Status Code

Invalid Requests

• Triggered by malformed requests, such as missing required parameters or incorrect data formats.
• Action: Review the request format and ensure all required parameters are correctly included.

404 Status Code

End of the Results!

• This code can signify two scenarios: Either you have reached the end of the available results.
• Action for End of Results: Adjust your query or parameters to access different data.

---

Understanding these error codes is essential for efficient debugging and ensuring smooth interaction with the GeoScraper API.