Rayobyte Documentation
  • Web Scraper API
    • Getting Started
    • Features
      • Proxy Geolocation
      • JavaScript Rendering
      • Custom Headers and Cookies
    • Billing & Usage
      • How We Charge You
      • Statistics
    • Reference
      • Response Codes
      • Timeout Settings
Powered by GitBook
On this page
  1. Web Scraper API
  2. Reference

Response Codes

PreviousReferenceNextTimeout Settings

Last updated 5 months ago

Understanding the response codes returned by our API is essential for troubleshooting and optimizing your scraping setup. Below is a list of the possible response codes you may encounter, along with their meanings:

Code

Message

200

Success

400

"Oops! Something's off with your request. Double-check your spelling and formatting, and maybe give our docs a quick read. Stuck? Give our support team a shout—they're pretty awesome!"

401

"Access denied! Looks like your API key is either on vacation or you've run out of funds. Recharge or reach out to support—they’ll help you get back in action!"

429

"Whoa, slow down there! We're juggling a lot of requests right now. Take a breather and retry—you won’t be charged for the hiccup."

500 Caught Ban

"Busted! The site’s anti-scraping defenses caught us this time. Share the URL with our support team, and we’ll help crack the code (don’t worry, no charges for failed attempts)."

500 Internal server error

"Yikes, something broke on our end. Try again or ping support—we’ve got your back. And hey, no charges for this little mishap!"

Need help deciphering a code or resolving an issue? Our is ready to assist! 🚀

support team