shipapis
StarSubmit an APISubmit API

IPWhois vs Parkleitsystem API

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

APIIPWhoisHEALTHY100Parkleitsystem APIHEALTHY86
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms231097
P95 · ms5984508
AuthapiKeynone
CORSyesno
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPWhois vs Parkleitsystem API: common questions

Which is more reliable, IPWhois or Parkleitsystem API?

Both are neck-and-neck — IPWhois and Parkleitsystem API 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, IPWhois or Parkleitsystem API?

IPWhois has the lower median latency in our checks — IPWhois responds in 23 ms versus Parkleitsystem API at 1097 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 IPWhois and Parkleitsystem API need an API key?

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

Can I call IPWhois and Parkleitsystem API from the browser?

Neither sends browser-friendly CORS headers reliably, so call IPWhois and Parkleitsystem API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are IPWhois and Parkleitsystem API free for commercial use?

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