latitudestringrequired
WGS84 latitude, or a comma-separated list of up to 100 latitudes.
https://api.sandbase.ai/v1/api/open-meteo/elevationTerrain elevation in meters for one or more coordinates, from a 90 m digital elevation model.
Your output will appear here
Complete the inputs, then click Run.
Terrain elevation in meters for one or more coordinates, from a 90 m digital elevation model.
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/elevation" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"latitude": "52.52,48.85", "longitude": "13.41,2.35"}'
| Name | Type | Required | Description |
|---|---|---|---|
latitude | string | Yes | WGS84 latitude, or a comma-separated list of up to 100 latitudes. |
longitude | string | Yes | WGS84 longitude, or a comma-separated list of up to 100 longitudes (positions aligned with latitude). |
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/elevation" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"latitude": "52.52,48.85",
"longitude": "13.41,2.35"
}
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.
latitudestringrequiredWGS84 latitude, or a comma-separated list of up to 100 latitudes.
longitudestringrequiredWGS84 longitude, or a comma-separated list of up to 100 longitudes (positions aligned with `latitude`).
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 ElevationThis 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/elevation 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: latitude (string) and longitude (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 Elevation 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.