shipapis
StarSubmit an APISubmit API

Fake JSON API vs ParlayAPI

Same instrument, two spec sheets — measured, not claimed.

APIFake JSON APIHEALTHY92ParlayAPIREACHABLE88
Uptime · 30d
Uptime · 90d99.44%87.5%
Uptime · 30d100%87.5%
P50 · ms342211
P95 · ms20561536
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree — limits not published
Rate limitUnpublished
In directory since2026-07-052026-10-04
operationalpartialdownno data

Fake JSON API vs ParlayAPI: common questions

Which is more reliable, Fake JSON API or ParlayAPI?

On our scheduled checks, Fake JSON API leads on measured uptime — Fake JSON API at 99.44% versus ParlayAPI at 87.5% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Fake JSON API or ParlayAPI?

ParlayAPI has the lower median latency in our checks — Fake JSON API responds in 342 ms versus ParlayAPI at 211 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Fake JSON API and ParlayAPI need an API key?

Fake JSON API needs no key, while ParlayAPI requires a free API key. If you want to start calling without signup, reach for Fake JSON API first.

Can I call Fake JSON API and ParlayAPI from the browser?

Only Fake JSON API is browser-friendly — it returns CORS headers over HTTPS. ParlayAPI needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Fake JSON API and ParlayAPI free for commercial use?

Fake JSON API has unclear commercial terms, and ParlayAPI has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.