/openmeteo/locations/search

POST /api/openmeteo/locations/search

Price: 1 credit

Search geographic locations by name and resolve them to coordinates

How to use it

Search locations by name to resolve them to coordinates for the weather endpoints. Returns matching places with geoname id, name, latitude, longitude, elevation, feature code, country and administrative-region names and ids, timezone, population, and postcodes. Use the returned latitude and longitude to query forecast, archive, air-quality, marine, or flood data.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• name string required — Location name to search for (examples: "Berlin", "San Francisco"; minLength: 1)
• count integer required — Max number of results to return (min: 1; max: 100)
• language string — Language for localized location fields (default: "en"; one of: "en", "de", "fr", "es", "it", "pt", "ru", "tr", "hi", "cn")

Response

• @type string (default: "OpenmeteoLocation")
• id integer required
• name string required
• latitude number required
• longitude number required
• elevation number nullable
• feature_code string nullable
• country string nullable
• country_code string nullable
• country_id integer nullable
• admin1 string nullable
• admin2 string nullable
• admin3 string nullable
• admin4 string nullable
• admin1_id integer nullable
• admin2_id integer nullable
• admin3_id integer nullable
• admin4_id integer nullable
• timezone string nullable
• population integer nullable
• postcodes array (default: [])

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No matching location found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.