shipapis
StarSubmit an APISubmit API

PostalPinCode vs ProblemsByVin

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

APIPostalPinCodeNEW—ProblemsByVinNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY 4.0
Free tierFree — no key requiredFree (weekly-refreshed static JSON datasets)
Rate limitUnpublishedUnpublished (static JSON files)
In directory since2026-07-052026-07-05
operationalpartialdownno data

PostalPinCode vs ProblemsByVin: common questions

Which is more reliable, PostalPinCode or ProblemsByVin?

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

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

Can I call PostalPinCode and ProblemsByVin from the browser?

Yes — both PostalPinCode and ProblemsByVin 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 PostalPinCode and ProblemsByVin free for commercial use?

PostalPinCode has unclear commercial terms, and ProblemsByVin 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.