shipapis
StarSubmit an APISubmit API

IFTTT vs OOPSpam

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

APIIFTTTNEW—OOPSpamNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished1000 req/window · 999 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

IFTTT vs OOPSpam: common questions

Which is more reliable, IFTTT or OOPSpam?

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

Do IFTTT and OOPSpam need an API key?

Neither needs a paid key — IFTTT is callable with no signup, and OOPSpam is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call IFTTT and OOPSpam from the browser?

Neither sends browser-friendly CORS headers reliably, so call IFTTT and OOPSpam from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are IFTTT and OOPSpam free for commercial use?

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