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

Stadia Maps Search API

The Search API from Stadia Maps — 3 operation(s) for search.

Stadia Maps Search API is one of 11 APIs that Stadia Maps 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, API documentation, authentication docs, and 1 JSON Schema.

This API exposes 3 operations across 3 paths, and defines 36 schemas. It is described by OpenAPI 3.2.0, at version 7.1.0.

Requests are made against 2 base URLs: https://api.stadiamaps.com, https://api-eu.stadiamaps.com.

3 operations 3 paths 36 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
7.1.0
Base URL
https://api.stadiamaps.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Stadia Maps Search API declares 1 security scheme for authenticating requests. An API key is passed in the query as api_key (ApiKeyAuth).

Paths & Operations 3

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

Search 3
GET
/geocoding/v1/search
Search for location and other info using a place name or address (forward geocoding).
search 16 params → 200400
GET
/geocoding/v1/search/structured
Find locations matching components (structured forward geocoding).
search-structured 23 params → 200400
POST
/geocoding/v1/search/bulk
Quickly run a batch of geocoding queries against the search or structured search endpoints.
search-bulk body → 200400

Schemas 36

The contract defines 36 schemas that model the data the API accepts and returns. The most detailed are peliasGeoJSONProperties (23 properties), searchStructuredQuery (23 properties), searchQuery (16 properties), peliasGeoJSONFeature (4 properties). Each schema is shown below with its type and property counts.

searchBoundaryCircleLat
number
The latitude of the center of a circle to limit the search to. Requires boundary.circle.lon.
searchFocusLat
number
The latitude of the point to focus the search on. This will bias results toward the focus point. Requires focus.point.lon.
limit
integer
The maximum number of results to return.
searchRegion
string
Typically the first administrative division within a country. For example, a US state or a Canadian province.
bulkSearchRequest
array
peliasLayer
string
Our database is organized into several layers (in the GIS sense of the term) as follows: - venue: Points of interest, businesses, and things with walls - addre…
searchSources
array
A list of sources to limit the search to.
searchBoundaryCircleLon
number
The longitude of the center of a circle to limit the search to. Requires boundary.circle.lat.
searchStructuredQuery
object
23 properties
peliasGeoJSONFeature
object
4 properties 2 required
searchCounty
string
Administrative divisions between localities and regions. Not commonly used as input to structured geocoding.
searchNeighborhood
string
Varies by area, but has a locally specific meaning (NOT always an official administrative unit).
searchBoundaryGID
string
The Pelias GID of an area to limit the search to.
searchText
string
The place name (address, venue name, etc.) to search for.
geoJSONGeometryBase
object
1 property 1 required
searchBoundaryRectMinLat
number
Defines the min latitude component of a bounding box to limit the search to. Requires all other boundary.rect parameters to be specified.
postalCode
string
A mail sorting code.
peliasLang
string
A BCP47 language tag which specifies a preference for localization of results. By default, results are in the default locale of the source data, but specifying…
peliasSource
string
Our database contains info from multiple sources. These identifiers can be used to either limit search results or to determine the relevance of a result.
bulkSearchResponse
object
3 properties 1 required
searchFocusLon
number
The longitude of the point to focus the search on. This will bias results toward the focus point. Requires focus.point.lat.
searchQuery
object
16 properties
searchBoundaryRectMaxLon
number
Defines the max longitude component of a bounding box to limit the search to. Requires all other boundary.rect parameters to be specified.
searchBoundaryCircleRadius
number
The radius of the circle (in kilometers) to limit the search to. Defaults to 50km if unspecified.
searchBoundaryRectMaxLat
number
Defines the max latitude component of a bounding box to limit the search to. Requires all other boundary.rect parameters to be specified.
searchBoundaryCountry
array
A list of countries to limit the search to. These may be either full names (ex: Canada), or an ISO 3116-1 alpha-2 or alpha-3 code. Prefer ISO codes when possib…
geocodingObject
object
4 properties
searchAddress
string
A street name, optionally with a house number.
searchCountry
string
A full name (ex: Canada), or a 2 or 3 character ISO code. Prefer ISO codes when possible.
searchLayers
array
A list of layers to limit the search to.
peliasGeoJSONProperties
object
23 properties
geoJSONPoint
searchLocality
string
The city, village, town, etc. that the place/address is part of.
searchBoundaryRectMinLon
number
Defines the min longitude component of a bounding box to limit the search to. Requires all other boundary.rect parameters to be specified.
searchBorough
string
A unit within a city (not widely used, but present in places like NYC and Mexico City).
peliasResponse
object
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

stadia-maps-search-api-openapi.yml Raw ↑

Other APIs Stadia Maps publishes across the network.

Stadia Maps Attributes API
Stadia Maps Autocomplete API
Stadia Maps Geospatial API
Stadia Maps Lookups API
Stadia Maps Match API
Stadia Maps Place API
Stadia Maps Reverse API
Stadia Maps Roads API
Stadia Maps Routes API
Stadia Maps Routing API
Where this information came from

This is an independent, third-party profile of Stadia Maps 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.