end_datestringrequired
End of the interval, `yyyy-mm-dd` (ISO 8601).
Open-Meteo Historical Weather
https://api.sandbase.ai/v1/api/open-meteo/archiveHistorical weather by coordinates and date range from the ERA5 reanalysis, back to 1940, with hourly and daily variables.
- Price
- $0.0001USD / call
- Method
- POST
- Response
- JSON
- Parameters
- 4 required · 10 optional
100 free calls / dayFirst 100 calls per day free (shared per organization) · Resets at 00:00 UTC. Pay per call after that.
Playground
Input
End of the interval, `yyyy-mm-dd` (ISO 8601).
WGS84 latitude of the location. Multiple coordinates can be comma-separated.
WGS84 longitude of the location (negative for the Americas). Multiple coordinates can be comma-separated.
Start of the interval, `yyyy-mm-dd` (ISO 8601).
Grid-cell preference for the coordinate. Default `land`. Allowed values: land, sea, nearest.
Comma-separated list of daily aggregation variables to return. Requires `timezone`. Common values: `temperature_2m_max`, `temperature_2m_min`, `temperature_2m_mean`, `precipitation_sum`, `rain_sum`, `snowfall_sum`, `weather_code`, `sunrise`, `sunset`, `sunshine_duration`, `wind_speed_10m_max`, `uv_i
Manual elevation (meters). Defaults to a 90m DEM.
Comma-separated list of hourly variables to return. Common values: `temperature_2m`, `relative_humidity_2m`, `dew_point_2m`, `apparent_temperature`, `precipitation`, `rain`, `showers`, `snowfall`, `weather_code`, `pressure_msl`, `cloud_cover`, `wind_speed_10m`, `wind_direction_10m`, `wind_gusts_10m`
Comma-separated reanalysis models, e.g. `era5`, `era5_land`, `ecmwf_ifs`, `cerra`. Default best match.
Precipitation unit. Default `mm`. Allowed values: mm, inch.
Temperature unit. Default `celsius`. Allowed values: celsius, fahrenheit.
Time output format. Default `iso8601`. Allowed values: iso8601, unixtime.
IANA time zone name (e.g. `Europe/Berlin`) or `auto` to resolve from coordinates. Defaults to `GMT`.
Wind speed unit. Default `kmh`. Allowed values: kmh, ms, mph, kn.
OutputReady
Your output will appear here
Complete the inputs, then click Run.
API README
Open-Meteo Historical Weather API
Historical weather by coordinates and date range from the ERA5 reanalysis, back to 1940, with hourly and daily variables.
The result is returned in outputs[0].data as the official Open-Meteo API response, unchanged.
Request
curl -X POST "https://api.sandbase.ai/v1/api/open-meteo/archive" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"end_date": "2024-01-07", "latitude": "52.52", "longitude": "13.41", "start_date": "2024-01-01", "daily": "temperature_2m_max,precipitation_sum", "timezone": "auto"}'
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
cell_selection | string | No | Grid-cell preference for the coordinate. Default land. |
daily | string | No | Comma-separated list of daily aggregation variables to return. Requires timezone. Common values: temperature_2m_max, temperature_2m_min, `temperature_2m_m |
elevation | string | No | Manual elevation (meters). Defaults to a 90m DEM. |
end_date | string | Yes | End of the interval, yyyy-mm-dd (ISO 8601). |
hourly | string | No | Comma-separated list of hourly variables to return. Common values: temperature_2m, relative_humidity_2m, dew_point_2m, apparent_temperature, `precipitat |
latitude | string | Yes | WGS84 latitude of the location. Multiple coordinates can be comma-separated. |
longitude | string | Yes | WGS84 longitude of the location (negative for the Americas). Multiple coordinates can be comma-separated. |
models | string | No | Comma-separated reanalysis models, e.g. era5, era5_land, ecmwf_ifs, cerra. Default best match. |
precipitation_unit | string | No | Precipitation unit. Default mm. |
start_date | string | Yes | Start of the interval, yyyy-mm-dd (ISO 8601). |
temperature_unit | string | No | Temperature unit. Default celsius. |
timeformat | string | No | Time output format. Default iso8601. |
timezone | string | No | IANA time zone name (e.g. Europe/Berlin) or auto to resolve from coordinates. Defaults to GMT. |
wind_speed_unit | string | No | Wind speed unit. Default kmh. |
Pricing
Flat price per call. Failed calls are not charged.
Start building
Send your first request
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/archive" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"daily": "temperature_2m_max,precipitation_sum",
"hourly": "temperature_2m,precipitation",
"models": "era5",
"end_date": "2024-01-07",
"latitude": "52.52",
"timezone": "auto",
"elevation": "38",
"longitude": "13.41",
"start_date": "2024-01-01",
"timeformat": "iso8601",
"cell_selection": "land",
"wind_speed_unit": "kmh",
"temperature_unit": "celsius",
"precipitation_unit": "mm"
}
SANDBASE_JSON
)
printf '%s\n' "$result"2. Authentication
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.
3. Parameters
latitudestringrequired
WGS84 latitude of the location. Multiple coordinates can be comma-separated.
longitudestringrequired
WGS84 longitude of the location (negative for the Americas). Multiple coordinates can be comma-separated.
start_datestringrequired
Start of the interval, `yyyy-mm-dd` (ISO 8601).
cell_selectionstring
Grid-cell preference for the coordinate. Default `land`.
Default: "land"
Possible values: land, sea, nearest
dailystring
Comma-separated list of daily aggregation variables to return. Requires `timezone`. Common values: `temperature_2m_max`, `temperature_2m_min`, `temperature_2m_mean`, `precipitation_sum`, `rain_sum`, `snowfall_sum`, `weather_code`, `sunrise`, `sunset`, `sunshine_duration`, `wind_speed_10m_max`, `uv_i
elevationstring
Manual elevation (meters). Defaults to a 90m DEM.
hourlystring
Comma-separated list of hourly variables to return. Common values: `temperature_2m`, `relative_humidity_2m`, `dew_point_2m`, `apparent_temperature`, `precipitation`, `rain`, `showers`, `snowfall`, `weather_code`, `pressure_msl`, `cloud_cover`, `wind_speed_10m`, `wind_direction_10m`, `wind_gusts_10m`
modelsstring
Comma-separated reanalysis models, e.g. `era5`, `era5_land`, `ecmwf_ifs`, `cerra`. Default best match.
precipitation_unitstring
Precipitation unit. Default `mm`.
Default: "mm"
Possible values: mm, inch
temperature_unitstring
Temperature unit. Default `celsius`.
Default: "celsius"
Possible values: celsius, fahrenheit
timeformatstring
Time output format. Default `iso8601`.
Default: "iso8601"
Possible values: iso8601, unixtime
timezonestring
IANA time zone name (e.g. `Europe/Berlin`) or `auto` to resolve from coordinates. Defaults to `GMT`.
wind_speed_unitstring
Wind speed unit. Default `kmh`.
Default: "kmh"
Possible values: kmh, ms, mph, kn
4. Response
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
Related APIs
| API | Price | Response |
|---|---|---|
Open-Meteo Historical WeatherThis 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
FAQ
How do I use the Open-Meteo Historical Weather API?
Send a POST request to https://api.sandbase.ai/v1/api/open-meteo/archive 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.
How much does the Open-Meteo Historical Weather API cost?
$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.
What parameters does the Open-Meteo Historical Weather API accept?
Required: end_date (string), latitude (string), longitude (string) and start_date (string). Optional: cell_selection (one of land, sea, nearest), daily (string), elevation (string), hourly (string), models (string) and precipitation_unit (one of mm, inch) and 4 more. The Parameters table and the Playground on this page list every field.
What does the Open-Meteo Historical Weather API return?
A JSON response returned in the same HTTP request (synchronous).
Do I need a Open-Meteo developer account or API key?
No. Open-Meteo Historical Weather 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.