The API request type (typically URL or FetchInput)
The API response type
OptionalextendedPostalCodesFor?: SearchIndexType[]The indexes for which results include extended postal codes.
Extended postal codes carry more detailed postal code information, including sub-divisions and hierarchical structures.
By default, extended postal codes are included for all indexes except Geo. Geographic entities
can have very long postal code lists, so you must request them explicitly when needed.
A regular postal code is "10001" (basic ZIP code), and an extended one "10001-1234" (ZIP+4 format).
Note that including them for geographies can significantly increase response size.
Optionallimit?: numberThe maximum number of results in a single response, which controls pagination.
Fuzzy search and geocoding page with cursor, as CommonGeocodeAndFuzzySearchParams.cursor describes.
Optionalmapcodes?: MapcodeType[]The mapcode representations to request for locations.
Mapcodes are short, human-friendly location codes that can represent any location on Earth to within a few meters. They're easier to remember and communicate than coordinates.
The mapcode types are:
Local: Short codes valid within a specific territory (e.g., "49.4V" in Netherlands)International: Codes that work globally (e.g., "NLD 49.4V")Alternative: Alternative representations for the same locationUse them for:
They apply to:
They cover:
// Search with mapcodes and specific geopolitical view
const detailedSearch: CommonPlacesParams<URL, Response> = {
geopoliticalView: 'IN', // India's perspective
mapcodes: ['Local', 'International'],
extendedPostalCodesFor: ['PAD', 'POI'],
limit: 5
};
// Address search with extended postal codes
const addressSearch: CommonPlacesParams<URL, Response> = {
extendedPostalCodesFor: ['Geo', 'PAD', 'Addr'],
limit: 15
};
The parameters the places services share.
Search, geocoding, and reverse geocoding use them to customise query behaviour, filter results, and control response formatting.