Skip to content
Docs

Status

How to check whether the API is up, and where incidents are published.

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
curl https://api.scrapercompany.com/health
200 response
{
  "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 failing for a while). Those failures are per request, are not charged, and are safe to retry with backoff.

Incidents

The public status page is at status.scrapercompany.com/status. It checks the website, the API and sign-in every 60 seconds, and keeps uptime history, incidents and an Atom feed that you can read without an account. We also email affected customers about incidents and planned maintenance. If something looks wrong, email [email protected] with an x-request-id from a failing call.

No uptime SLA on self-serve plans

Enterprise terms are agreed individually.

Questions about this page?

Send the page link and your question, and the team will answer.

Email support