yesno.wtf API
- Status
- Working
- API key
- Not needed
- Browser calls
- Runs in the browser
- Latency
- 766 ms
- Docs
- yesno.wtf ↗
Build snapshot, not live. One verifier run on , from the machine that built this site. How we check
Example request
GEThttps://yesno.wtf/api
Sent from your browser straight to yesno.wtf. No proxy: this site never sees the request or the answer.
Copy the request
curl -s 'https://yesno.wtf/api'const res = await fetch("https://yesno.wtf/api");
if (!res.ok) throw new Error(`HTTP ${res.status}`);
const data = await res.json();
console.log(data);import requests
res = requests.get("https://yesno.wtf/api", timeout=10)
res.raise_for_status()
print(res.json())Response stored by the verifier
This is what yesno.wtf answered when the verifier sent the request above on : HTTP 200, application/json. Arrays are cut to two items and long strings are shortened. It comes from the build snapshot.
{
"answer": "yes",
"forced": false,
"image": "https://yesno.wtf/assets/yes/7-653c8ee5d3a6bbafd759142c9c18d76c.gif"
}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 JSON body must contain the field "answer".
Last check: — passed, HTTP 200 in 766 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 yesno.wtf API need an API key?
No. The sample request on this page was answered without a key, token or account.
Can I call the yesno.wtf API from the browser?
Yes. yesno.wtf answered our verifier with an Access-Control-Allow-Origin header on Oct 3, 2026, so a fetch call from a web page can read the response.
Is the yesno.wtf API working?
At the check on Oct 3, 2026 it returned HTTP 200 with the expected data in 766 ms. The status at the top of this page shows the most recent result we have.