namestringrequired
Location name or postal code. Append `, ` or `, ` to narrow results.
https://api.sandbase.ai/v1/api/open-meteo/geocodingLook up places by name and get coordinates, country, timezone, population and elevation for use with the weather APIs.
Your output will appear here
Complete the inputs, then click Run.
Look up places by name and get coordinates, country, timezone, population and elevation for use with the weather APIs.
The result is returned in outputs[0].data as the official Open-Meteo API response, unchanged.
curl -X POST "https://api.sandbase.ai/v1/api/open-meteo/geocoding" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "Berlin"}'
| Name | Type | Required | Description |
|---|---|---|---|
count | integer | No | Maximum number of results (1-100). Default 10. |
countryCode | string | No | ISO-3166-1 alpha-2 country code to filter results. |
format | string | No | Response format. Default json. |
language | string | No | Two-letter language code for translated names. Default en. |
name | string | Yes | Location name or postal code. Append , or , to narrow results. |
Flat price per call. Failed calls are not charged.
Start building
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/open-meteo/geocoding" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"name": "Berlin",
"count": 5,
"format": "json",
"language": "en",
"countryCode": "DE"
}
SANDBASE_JSON
)
printf '%s\n' "$result"Set your SandBase API key in your server environment. Requests use Bearer authentication.
export SANDBASE_API_KEY="YOUR_API_KEY"Keep your key on the server. Do not expose it in browser code.
namestringrequiredLocation name or postal code. Append `, ` or `, ` to narrow results.
countintegerMaximum number of results (1-100). Default 10.
Default: 10
countryCodestringISO-3166-1 alpha-2 country code to filter results.
formatstringResponse format. Default `json`.
Default: "json"
Possible values: json, protobuf
languagestringTwo-letter language code for translated names. Default `en`.
Default: "en"
Saved example response for this API; no live request is made when viewing it.
No saved response has been published. Run the API in Playground to inspect its response.
Explore more
| API | Price | Response |
|---|---|---|
Open-Meteo GeocodingThis API Open-Meteo | $0.0001 per call | JSON |
Open-Meteo | $0.0001 per call | JSON |
Open-Meteo | $0.0001 per call | JSON |
Open-Meteo | $0.0001 per call | JSON |
Open-Meteo | $0.0001 per call | JSON |
Open-Meteo | $0.0001 per call | JSON |
Questions
Send a POST request to https://api.sandbase.ai/v1/api/open-meteo/geocoding with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.
$0.0001 per call. Every organization gets 100 free calls per UTC day, shared across eligible SandBase APIs including this one; after that each call is billed at this price from your SandBase balance. There is no subscription.
Required: name (string). Optional: count (integer), countryCode (string), format (one of json, protobuf) and language (string). The Parameters table and the Playground on this page list every field.
A JSON response returned in the same HTTP request (synchronous).
No. Open-Meteo Geocoding runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for Open-Meteo API access separately.