HTTP Cats API
- Status
- Working
- API key
- Not needed
- Browser calls
- Server only
- Latency
- 173 ms
- Docs
- http.cat ↗
Build snapshot, not live. One verifier run on , from the machine that built this site. How we check
Example request
GEThttps://http.cat/200
Copy the request
curl -s 'https://http.cat/200'const res = await fetch("https://http.cat/200");
if (!res.ok) throw new Error(`HTTP ${res.status}`);
const data = await res.blob();
console.log(data);import requests
res = requests.get("https://http.cat/200", timeout=10)
res.raise_for_status()
print(len(res.content))Response stored by the verifier
This is what http.cat answered when the verifier sent the request above on : HTTP 200, image/jpeg. The body is an image, so it is not reproduced here. It comes from the build snapshot.
Availability
Up 1 of 1 day checked · 30-day window
What counts as up for this API: an answer within five seconds, a 2xx status, and the content type must be an image.
Last check: — passed, HTTP 200 in 173 ms.
The check runs from our infrastructure, not from where you are. If you need certainty, send the request yourself above. How the verifier works.
Questions
Does the HTTP Cats API need an API key?
No. The sample request on this page was answered without a key, token or account.
Can I call the HTTP Cats API from the browser?
Not directly. http.cat did not send an Access-Control-Allow-Origin header to our verifier on Oct 3, 2026, so browsers block the response. Call it from a server or a serverless function.
Is the HTTP Cats API working?
At the check on Oct 3, 2026 it returned HTTP 200 with the expected data in 173 ms. The status at the top of this page shows the most recent result we have.