Places API

Places API for server-side search.

Open Places API returns place search results from open Overture data through one authenticated HTTP endpoint. Send search text, a location, and a radius from your backend, then get JSON back.

Start for free Read the docs Compare Google Places

One backend call.

The API is intentionally narrow: one search endpoint, bearer authentication, quota headers, and JSON results. Keep the key on your server and use the response in your app, workflow, marketplace, CRM, or internal tool.

curl -G "https://api.openplacesapi.com/v1/places" \
  --data-urlencode "q=coffee" \
  --data-urlencode "lat=40.7128" \
  --data-urlencode "lon=-74.0060" \
  --data-urlencode "radius_mi=25" \
  -H "Authorization: Bearer $OPEN_PLACES_API_KEY"

What the API gives you.

Overture-backed places

Search a hosted index built from Overture Places data, currently covering 39 million places across 18 selected countries and territories.

Server-side integration

No frontend key exposure and no browser SDK requirement. Use curl, fetch, Python, or whatever your backend already runs.

Predictable quotas

Plans have hard monthly caps. If quota runs out, the API stops instead of silently creating overage spend.

Scoped search

Every query is constrained by a location and radius, which keeps the product focused on local search use cases.

Custom layers

Add account-owned place records, corrections, suppressions, and presets on top of the shared base layer.

OpenAPI contract

The public contract is published as OpenAPI 3.1 so teams can inspect, generate clients, or wire tests around it.

When it is the right fit.

Good fit	Probably not a fit
Backend place search for store locators, marketplaces, CRMs, operations tools, and local search workflows.	Turn-by-turn routing, map tiles, mobile SDKs, autocomplete widgets, or global address validation.
Teams that want open-data foundations and predictable pricing.	Teams that need every feature of a full maps platform from one vendor.

Places API FAQ.

What is a Places API?

A Places API lets software search for real-world places, such as businesses, landmarks, venues, and addresses, and return structured JSON that an application can use.

Is Open Places API a geocoding API?

Open Places API is focused on place search near a latitude and longitude. It is not trying to replace a full geocoding, routing, tiles, or mobile maps SDK.

Can I call it from a browser?

The public API is designed for server-side calls with a bearer API key. Browser frontends should call your backend so the API key stays private.

Does it replace Google Places?

It can replace Google Places for products that only need backend place search and JSON results. It is narrower than Google Maps Platform by design.