Open Places API Coverage
Overture Places coverage, scoped for production.
Open Places API currently serves 39 million Overture-backed places across 18 selected countries and territories. The coverage promise is deliberately narrower than global: a listed country answers immediately, completely, and predictably.
Supported country set.
Europe
Asia
Japan , South Korea , Singapore , Malaysia
Caribbean and Central America
Dominican Republic , Costa Rica , Puerto Rico , Jamaica , Bahamas
What coverage means in the API.
| Term | Meaning |
|---|---|
| Production coverage | The selected country set the public API is prepared to serve in normal operation. |
| Location scope | Every search includes text, latitude, longitude, and radius so coverage can be checked against a bounded area. |
| Ready coverage | Listed countries are prepared to answer before customer traffic arrives. No first-request warm-up. |
coverage_not_ready | A retryable operational error returned when required coverage is unavailable, instead of partial search results. |
Why the coverage claim is narrow.
Overture publishes broad open places data, but a production API still has to ingest, index, validate, and monitor everything it serves. Open Places API starts with a selected coverage set so that when the API says it serves a region, it's ready before customer traffic arrives.
Coverage FAQ.
Does Open Places API have global coverage?
No. The current production coverage is intentionally scoped to 18 selected countries and territories. The product should not be treated as a global places API yet.
What does production coverage mean?
Production coverage means the listed countries are ready to answer immediately in normal operation. If a search can't be served, the API returns a clear retryable error instead of partial results.
What happens when coverage is not ready?
If required production coverage is unavailable, the public API returns a retryable coverage_not_ready error instead of returning partial results.
Can custom layers add places outside the base coverage area?
Account-owned layers are designed for scoped product-specific records, but broad geographic availability still depends on the supported production coverage contract.