shipapis
StarSubmit an APISubmit API

IFTTT vs PubMed E-utilities

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

APIIFTTTHEALTHY92PubMed E-utilitiesHEALTHY68
Uptime · 30d
Uptime · 90d100%75.5%
Uptime · 30d100%66.7%
P50 · ms6821259
P95 · ms12624903
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished3 req/window · 1 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

IFTTT vs PubMed E-utilities: common questions

Which is more reliable, IFTTT or PubMed E-utilities?

On our scheduled checks, IFTTT leads on measured uptime — IFTTT at 100% versus PubMed E-utilities at 75.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, IFTTT or PubMed E-utilities?

IFTTT has the lower median latency in our checks — IFTTT responds in 682 ms versus PubMed E-utilities at 1259 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 PubMed E-utilities need an API key?

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

Can I call IFTTT and PubMed E-utilities from the browser?

Only PubMed E-utilities 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 PubMed E-utilities free for commercial use?

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