Colombia Public API vs GeoJS

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms840107
P95 · ms3006722
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree, no API key required
Rate limitUnpublishedUnpublished (no enforced limit stated)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Colombia Public API vs GeoJS: common questions

Which is more reliable, Colombia Public API or GeoJS?

Both are neck-and-neck — Colombia Public API and GeoJS 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, Colombia Public API or GeoJS?

GeoJS has the lower median latency in our checks — Colombia Public API responds in 840 ms versus GeoJS at 107 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 Colombia Public API and GeoJS need an API key?

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

Can I call Colombia Public API and GeoJS from the browser?

Yes — both Colombia Public API and GeoJS 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 Colombia Public API and GeoJS free for commercial use?

Colombia Public API has unclear commercial terms, and GeoJS 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.