---
title: "Search for places. Complete words required."
method: GET
path: "/find_places"
tags: ["Location endpoints"]
---

# Search for places. Complete words required.

`GET /find_places`

## Search for places

You can use this endpoint to obtain `place_id` of the location you want, to be used in `point` endpoint.
The response also contains detailed information about the location, such as coordinates, timezone and the country the place belongs to.

Unlike the `/find_places_prefix` endpoint, complete words are required here. You can search for cities,
mountains, lakes, countries, ZIP codes, etc. The response can contain multiple places, sorted by relevance.
You can then identify the one you want by coordinates, country, or the administrative area.

## Query parameters

- `text` string, required — Place name or ZIP code
- `language` 'cs' | 'en' | 'de' | 'es' | 'fr' | 'pl' | 'pt'
- `key` string — Your unique API key. You can either specify it in this parameter, or set it in `X-API-Key` header.

## Response `200`

Successful Response

- FindPlacesModel[]
  - `name` string — name of the place
  - `place_id` string — unique identifier of the place, which can be used in /point and /map endpoints
  - `adm_area1` string, nullable — first-level administrative area (a US state, for example)
  - `adm_area2` string, nullable — second-level administrative area (a US county, for example)
  - `country` string, nullable — name of the country
  - `lat` string — Latitude of the point, always in the format \<float><N/S>, for example ``23.5S``
  - `lon` string — Longitude of the point, always in format \<float><E/W>, for example ``23.5W``
  - `timezone` string, nullable — Timezone of the point in tzinfo format.
  - `type` string — The character of the place. May be one of the following values: * administrative areas (states, counties, districts...): ``administrative_area`` * country: ``country`` * a different political entity from a country (for example, a dependent teritory): ``political_entity`` * villages, towns and cities: ``settlement`` * air industry locations: ``airbase``, ``airfield``, ``heliport``, ``airport``, ``airport_terminal`` * places related to water: ``bay``, ``channel``, ``fjord``, ``lake``, ``pond``, ``falls``, ``gulf``, ``harbor``, ``reservoir``, ``sea``, ``dam``, ``cape``, ``island``, ``peninsula`` * places related to mountain areas: ``hill``, ``mountain``, ``peak``, ``valley``, ``volcano``, ``canyon`` * other places related to nature: ``park``, ``reserve``, ``resort``, ``desert`` * places based on postcodes: ``postcode``

## Other responses

- `400` — Error in passed parameter.
- `402` — Maximum requests per day limit exceeded.
- `403` — API key not not specified or invalid.
- `422` — Validation Error
- `429` — Maximum requests per minute limit exceeded.

---

[API](https://skmtc.dev/meteosource/apis/interactive-documentation-for-your-premium-plan.md) · [All operations](https://skmtc.dev/meteosource/apis/interactive-documentation-for-your-premium-plan/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/meteosource/interactive-documentation-for-your-premium-plan/revisions/639d912e4ae5/schema)