How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Google Places Search API

Operations for searching and autocompleting places.

Google Places Search API is one of 2 APIs that Google Places publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Search. The published artifact set on APIs.io includes an OpenAPI specification, code examples, API documentation, and 1 JSON Schema.

This API exposes 3 operations across 3 paths, and defines 16 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://places.googleapis.com/v1.

3 operations 3 paths 16 schemas 3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://places.googleapis.com/v1
Authentication
API Key, API Key, OAuth 2.0
Resource Areas
1

Authentication & Security 3

Google Places Search API declares 3 security schemes for authenticating requests. An API key is passed in the header as X-Goog-Api-Key (ApiKeyAuth). An API key is passed in the query as key (ApiKeyQuery). It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 1 scope. By default, every request must be authenticated.

  • ApiKeyAuth — Google Maps Platform API key passed in the X-Goog-Api-Key header.
  • ApiKeyQuery — Google Maps Platform API key passed as the key query parameter.
  • OAuth2 — OAuth 2.0 bearer token authorization for the Google Maps Platform.

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 POST. Each is listed below with its method, path, parameters, and response codes.

Search 3

Operations for searching and autocompleting places.

POST
/places:searchNearby
Google Places Search Nearby
searchNearbyPlaces 1 param body → 200400403
POST
/places:searchText
Google Places Search Text
searchTextPlaces 1 param body → 200400403
POST
/places:autocomplete
Google Places Autocomplete
autocompletePlaces 1 param body → 200400

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are Place (19 properties), TextSearchRequest (9 properties), Review (7 properties), NearbySearchRequest (7 properties). Each schema is shown below with its type and property counts.

TextSearchRequest
object
Request body for a Text Search.
9 properties 1 required
Place
object
A place returned by the Google Places API, such as an establishment or point of interest.
19 properties
SearchResponse
object
A response containing a list of places.
1 property
OpeningHours
object
Information about the operating hours of a place.
3 properties
AuthorAttribution
object
Attribution for the author of a review or photo.
3 properties
Circle
object
A circle defined by a center point and a radius in meters.
2 properties
LocalizedText
object
Localized text in a particular language.
2 properties
LatLng
object
A latitude/longitude pair expressed in degrees.
2 properties
AutocompleteResponse
object
Response from an Autocomplete request.
1 property
Review
object
A user review of a place.
7 properties
Photo
object
A photo associated with a place.
4 properties
AutocompleteRequest
object
Request body for an Autocomplete request.
6 properties 1 required
NearbySearchRequest
object
Request body for a Nearby Search.
7 properties 1 required
TimePoint
object
A point in time when a place opens or closes.
3 properties
Suggestion
object
A single autocomplete suggestion.
2 properties
Error
object
A standard Google API error response.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

google-places-search-api-openapi.yml Raw ↑

Other APIs Google Places publishes across the network.

Google Places Places API
Where this information came from

This is an independent, third-party profile of Google Places Search API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.