The API
An HTTP endpoint with a token. Best when you are writing the client anyway and want control over modules and options.
You give us a URL. We fetch it and return the page.
Proxy selection, browser rendering, ban detection and retries all happen on our side. There is no proxy to configure and nothing to rotate.
curl "http://api.scraping.rayobyte.com/?token=YOUR_TOKEN&url=https://example.com"The API
An HTTP endpoint with a token. Best when you are writing the client anyway and want control over modules and options.
Web Unblocker
The same engine behind a proxy port. Point any existing client at it and it works, with no code changes at all.
With proxies you own the request. You choose the exit IP, set the headers, handle the blocks and parse the result.
Here you own none of that. That is the trade: less control, far less to maintain.
| Proxies | Scraping API | |
|---|---|---|
| Who sends the request | You | Us |
| Choose the exit IP | Yes | No |
| Handle blocks and retries | You | Us |
| Billed by | Bandwidth | Per scrape |
| Sub-accounts | Yes | No, one token |
Was this page helpful?
Thanks — that helps us fix it.