Model Updates and Data Availability

You can retrieve the update times for each individual model via the API. However, these times do not directly correlate with the update times in the Forecast API, as Open-Meteo automatically selects the most appropriate weather model for each location (referred to as "Best Match"). The table above provides an API link for each model, returning a JSON object with the following fields:

• last_run_initialisation_time: The model's initialization time or reference time represented as a Unix timestamp (e.g., 1724796000 for Tue Aug 27, 2024, 22:00:00 GMT+0000).
• last_run_modification_time: The time when the data download and conversion were completed, which does not indicate when the data became available on the API.
• last_run_availability_time: The time when the data is actually accessible on the API server. Important: Open-Meteo utilizes multiple redundant API servers, so there may be slight differences between them while the data is being copied. To ensure all API calls use the most recent data, please wait 10 minutes after the availability time.
• temporal_resolution_seconds: The temporal resolution of the model in seconds. By default, the API interpolates the data to a 1-hour resolution. However, the underlying model may only provide data in 3 or 6-hourly steps. A value of 3600 indicates that the data is 1-hourly.
• update_interval_seconds: The typical time interval between model updates, such as 3600 seconds for a model that updates every hour.

Additional attributes, such as spatial resolution, area, grid systems, and more, will be added in the future.