shipapis
StarSubmit an APISubmit API

IFTTT vs ipify

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

APIIFTTTUNMONITORED—ipifyHEALTHY—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedn/a
Free tierFree — limits not publishedUnlimited
Rate limitUnpublishedNone
In directory since2026-07-052026-05-02
operationalpartialdownno data

IFTTT vs ipify: common questions

Which is more reliable, IFTTT or ipify?

Only ipify is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do IFTTT and ipify need an API key?

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

Can I call IFTTT and ipify from the browser?

Only ipify 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 ipify free for commercial use?

IFTTT has unclear commercial terms, and ipify allows commercial use on its free tier. 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.