Status
How to check whether the API is up, and how incidents are communicated.
Health endpoint
GET https://api.scrapercompany.com/health needs no API key and returns 200 while the API is serving requests. Use it for uptime checks.
curl https://api.scrapercompany.com/health{
"status": "ok",
"version": "1.0.0",
"commit": "9627dba1c0de",
"started_at": "2026-09-30T21:04:11+00:00"
}commit is the first 12 characters of the deployed build's git commit (null when the build does not record one) and started_at is when the serving process started, in UTC. A change in either means a new deploy or a restart; the check itself does no upstream work, so it stays fast and free.
A healthy API can still get 502 from an individual source (for example an OTA blocking requests for a while). Those failures are per request, are not charged, and are safe to retry with backoff.
Incidents
There is no public status page yet. During the beta, we email affected customers about incidents and planned maintenance. If something looks wrong, email support@scrapercompany.com with an x-request-id from a failing call.