shipapis
StarSubmit an APISubmit API

IFTTT vs OnSched Consumer API

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

APIIFTTTHEALTHY92OnSched Consumer APIHEALTHY88
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms682722
P95 · ms12621890
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IFTTT vs OnSched Consumer API: common questions

Which is more reliable, IFTTT or OnSched Consumer API?

Both are neck-and-neck — IFTTT and OnSched Consumer API each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, IFTTT or OnSched Consumer API?

IFTTT has the lower median latency in our checks — IFTTT responds in 682 ms versus OnSched Consumer API at 722 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 IFTTT and OnSched Consumer API need an API key?

IFTTT needs no key, while OnSched Consumer API requires a free API key. If you want to start calling without signup, reach for IFTTT first.

Can I call IFTTT and OnSched Consumer API from the browser?

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

Are IFTTT and OnSched Consumer API free for commercial use?

IFTTT has unclear commercial terms, and OnSched Consumer API 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.