BetTip
Open Data
Lottery draw results for UK49s, Gosloto and South African National Lottery
Unofficial US Federal Government API Development
Checked 4 days ago: not responding
API key
Not required
HTTPS
Not supported
Browser calls
No, needs a proxy
Status
Failing · 0/100
Last checked 2026-09-18. Measured independently, not self-reported by the provider.
A starting template for 18F. Replace ENDPOINT with the path from the official documentation, which we link above rather than guess at.
# No authentication required.
curl -s "http://18f.github.io/ENDPOINT" \
-H "Accept: application/json"This API does not send CORS headers, so a browser will block a direct call from your front end. Call it from your server, or put a small proxy in front of it.
This API is served over plain HTTP. Browsers block HTTP requests made from an HTTPS page, so you will need a server-side call.
Aggregated from one public source (public-apis), then normalised and checked by us. If something here is wrong, tell us and we will correct it.
Open Data
Lottery draw results for UK49s, Gosloto and South African National Lottery
Open Data
Cross-brand carbide insert grade equivalents by ISO application class
Open Data
Hardware end-of-sale and end-of-service-life dates by part number, source-linked
Open Data
Daily travel-safety scores and 5 risk pillars for 248 countries, from gov advisories and indices
Open Data
Fixed Philippine PCSO draw results and schedules with row-level provenance
Open Data
Extract structured data from any website
Answered from what our own scheduled checks found, not from the provider's marketing.
18F is listed in our free catalogue and required no credential when we called it. It needs no authentication at all, so you can send a request without signing up. Free tiers can still carry rate limits or non-commercial terms, so check the provider's own terms before shipping.
No. We called 18F on 2026-09-18 with no key, no token and no Authorization header, and it responded. That is what puts it in our no-key collection.
Not directly. 18F did not return CORS headers when we checked, so the browser will block your page from reading the response even though the request itself succeeds. Call it from a server, or put a small proxy in front of it.
Not at our last check on 2026-09-18. 18F did not respond successfully, which is why it is marked as down here. This may be temporary; we re-check on a schedule and the badge above reflects the most recent run.
No. 18F was only reachable over plain HTTP when we checked. Browsers block HTTP requests made from an HTTPS page, so this will fail in production unless you call it from a server instead.