shipapis
StarSubmit an APISubmit API

GOV.UK Pay API vs Twelve Data

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

APIGOV.UK Pay APINEW—Twelve DataREACHABLE—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSnoyes
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

GOV.UK Pay API vs Twelve Data: common questions

Which is more reliable, GOV.UK Pay API or Twelve Data?

On our scheduled checks, Twelve Data leads on measured uptime — GOV.UK Pay API at —% versus Twelve Data 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 GOV.UK Pay API and Twelve Data need an API key?

Both ask you to authenticate — GOV.UK Pay API uses an API key and Twelve Data 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 GOV.UK Pay API and Twelve Data from the browser?

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

Are GOV.UK Pay API and Twelve Data free for commercial use?

GOV.UK Pay API has unclear commercial terms, and Twelve Data 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.