Phonepe API vs SHARE

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms487353
P95 · ms1085759
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Phonepe API vs SHARE: common questions

Which is more reliable, Phonepe API or SHARE?

Both are neck-and-neck — Phonepe API and SHARE each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Phonepe API or SHARE?

SHARE has the lower median latency in our checks — Phonepe API responds in 487 ms versus SHARE at 353 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 Phonepe API and SHARE need an API key?

SHARE needs no key, while Phonepe API requires a free API key. If you want to start calling without signup, reach for SHARE first.

Can I call Phonepe API and SHARE from the browser?

Yes — both Phonepe API and SHARE 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 Phonepe API and SHARE free for commercial use?

Phonepe API has unclear commercial terms, and SHARE 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.