System status
A live check of the API and the services around it. This page asks our backend directly each time you open it, and again every minute.
- Checking
API
REST API at api.scrapeeverything.com
- Checking
Dashboard
Sign-in, keys, usage and billing pages
- Checking
Payments (2328)
Crypto checkout for credit packs through 2328 (2328.io), our crypto payment processor
- Checking
Card payments (iyzico)
Credit card checkout for credit packs through iyzico, confirmed by your bank with 3D Secure
- Checking
Demo
The live demo on the home page
How failures are handled
Platforms change and block traffic. When a request fails for a reason that is not a final answer, you do not pay for it.
- Blocks, timeouts and our errors are refunded. Credits are reserved when a request starts and returned automatically before the response is sent when the failure is on the platform's side or ours.
- Final answers are billed. A definitive NOT_FOUND or PRIVATE_ACCOUNT result is charged, because the lookup completed. Retrying it returns the same answer.
- Every JSON response has a request_id. It is in the response body and the X-Request-Id header. Include it when you contact support and we can find the exact request.
- Full list of codes and retry advice: Errors in the docs.
| Status | Code | Meaning |
|---|---|---|
| 503 | TARGET_BLOCKED | The platform blocked every attempt. |
| 503 | PARSE_ERROR | The platform returned a response we could not read. |
| 503 | PROXY_CONNECT_FAILED | A network error occurred on our side. |
| 503 | TIMEOUT | The platform did not answer in time. |
| 503 | NO_PROXY_AVAILABLE | Capacity is temporarily exhausted. |
| 500 | INTERNAL_ERROR | Something went wrong on our side. |
All of these are refunded in full.
Incidents
No public incident history yet. Major incidents will be posted here and in the changelog.
Seeing errors that this page does not explain? Contact us with a request_id.