shipapis
StarSubmit an APISubmit API

The SMS Works API vs xfetch

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

APIThe SMS Works APINEW—xfetchNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

The SMS Works API vs xfetch: common questions

Which is more reliable, The SMS Works API or xfetch?

On our scheduled checks, xfetch leads on measured uptime — The SMS Works API at —% versus xfetch 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 The SMS Works API and xfetch need an API key?

Both ask you to authenticate — The SMS Works API uses an API key and xfetch uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call The SMS Works API and xfetch from the browser?

Yes — both The SMS Works API and xfetch send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are The SMS Works API and xfetch free for commercial use?

The SMS Works API has unclear commercial terms, and xfetch 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.