Previous Model Runs

Access prior model-run forecasts for verification and run-to-run comparison.

GET https://api.aisa.one/apis/v1/openmeteo/previous-runs

Previous Model Runs

cURL

curl --request GET \
  --url https://api.aisa.one/apis/v1/openmeteo/previous-runs \
  --header 'Authorization: Bearer <token>'

200

{
  "latitude": 52.52,
  "longitude": 13.41,
  "generationtime_ms": 0.7,
  "utc_offset_seconds": 0,
  "timezone": "GMT",
  "elevation": 38,
  "hourly_units": {
    "time": "iso8601",
    "temperature_2m": "°C",
    "temperature_2m_previous_day1": "°C"
  },
  "hourly": {
    "time": [
      "2024-01-01T00:00"
    ],
    "temperature_2m": [
      2.1
    ],
    "temperature_2m_previous_day1": [
      2.4
    ]
  }
}

Compare the current forecast against earlier model runs for the same valid time — useful for forecast verification and run-to-run stability checks. Request a variable and its earlier runs by appending _previous_dayN (e.g. temperature_2m together with temperature_2m_previous_day1, temperature_2m_previous_day2) to your hourly or daily lists.

The response returns grid-cell metadata and the requested resolution blocks, each with a time array, one array per variable (including the _previous_dayN series), and a matching *_units object.

Example: GET /apis/v1/openmeteo/previous-runs?latitude=52.52&longitude=13.41&hourly=temperature_2m,temperature_2m_previous_day1.

Billing: $0.00015 per call (150 micros USD), metered per request. All Open-Meteo endpoints are GET pass-through — authenticate with your AIsa API key as a bearer token (the same key used across every AIsa /apis/* endpoint); AIsa handles provider access.

Authorizations

Authorization · string · header · required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Query Parameters

latitude · string · required

WGS84 latitude of the location. Multiple coordinates can be comma-separated.

Example:

"52.52"

longitude · string · required

WGS84 longitude of the location (negative for the Americas). Multiple coordinates can be comma-separated.

Example:

"13.41"

hourly · string

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, shortwave_radiation, visibility. Append _previous_day1, _previous_day2, ... to a variable to fetch earlier runs (e.g. temperature_2m_previous_day1).

Example:

"temperature_2m,temperature_2m_previous_day1"

daily · string

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_index_max.

Example:

"temperature_2m_max,temperature_2m_max_previous_day1"

forecast_days · integer · default: 7

Number of forecast days to return (0-16). Default 7.

Example:

7

past_days · integer · default: 0

Number of past days to include (0-92). Default 0.

start_date · string<date>

Start of the interval, yyyy-mm-dd (ISO 8601).

Example:

"2024-01-01"

end_date · string<date>

End of the interval, yyyy-mm-dd (ISO 8601).

Example:

"2024-01-07"

temperature_unit · enum<string> · default: celsius

Temperature unit. Default celsius.

Available options: celsius, fahrenheit

wind_speed_unit · enum<string> · default: kmh

Wind speed unit. Default kmh.

Available options: kmh, ms, mph, kn

precipitation_unit · enum<string> · default: mm

Precipitation unit. Default mm.

Available options: mm, inch

timeformat · enum<string> · default: iso8601

Time output format. Default iso8601.

Available options: iso8601, unixtime

models · string

Comma-separated forecast models. Default best match.

Example:

"best_match"

timezone · string

IANA time zone name (e.g. Europe/Berlin) or auto to resolve from coordinates. Defaults to GMT.

Example:

"Europe/Berlin"

cell_selection · enum<string> · default: land

Grid-cell preference for the coordinate. Default land.

Available options: land, sea, nearest

Response

200 - application/json

Current and previous-run forecasts for the coordinate.

The response is of type object.