Open-Meteo Weather Forecast (Public Test)

Forecast queries with multi-location, multi-model, 15-minute, date-window and export options.

Selected price
$0.01 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Optional parameters (38)
WGS84 latitude: one number or comma-separated values, e.g. 31.23,39.90; each value must be -90 to 90. Required with its coordinate counterpart unless bounding_box is used. Latitude and longitude counts must match. Range and list alignment are checked by Open-Meteo.
WGS84 longitude: one number or comma-separated values, e.g. 121.47,116.40; each value must be -180 to 180. Required with its coordinate counterpart unless bounding_box is used. Latitude and longitude counts must match. Range and list alignment are checked by Open-Meteo.
Optional area query in south,west,north,east order, e.g. 31.20,121.40,31.30,121.50. Use instead of latitude/longitude. South<north, west<east; coordinate ranges apply. Choose an explicit model supporting grid queries; best_match and some grids may reject bounding boxes. One fixed timezone only; auto is unsupported. Subject to upstream location/grid-cell limits.
Comma-separated current variable identifiers, e.g. temperature_2m,relative_humidity_2m,weather_code. Accepts all identifiers supported by this operation and selected models, not just these examples. Variable availability depends on model, region and horizon. No former 256-character selection cap; total request size still applies.
Comma-separated hourly variable identifiers, e.g. temperature_2m,relative_humidity_2m,wind_speed_10m. Accepts all identifiers supported by this operation and selected models, not just these examples. Variable availability depends on model, region and horizon. No former 256-character selection cap; total request size still applies.
Comma-separated daily variable identifiers, e.g. temperature_2m_max,temperature_2m_min,sunrise,sunset. Accepts all identifiers supported by this operation and selected models, not just these examples. Variable availability depends on model, region and horizon. No former 256-character selection cap; total request size still applies. Supply timezone when daily is selected.
Comma-separated minutely_15 variable identifiers, e.g. temperature_2m,precipitation,wind_speed_10m. Accepts all identifiers supported by this operation and selected models, not just these examples. Variable availability depends on model, region and horizon. No former 256-character selection cap; total request size still applies. Native 15-minute coverage is regional; other regions may use hourly interpolation.
Legacy convenience flag: true returns the predefined current-weather group and current_weather response section. Prefer current for explicit variable selection; when both are supplied true takes precedence.
IANA timezone, auto, or a comma-separated list for multiple locations. Default GMT. One timezone applies to all locations, otherwise count must match coordinates. Required with daily. Bounding-box queries allow one fixed timezone and do not allow auto.
Forecast calendar days, default 7; up to 16. Native model coverage may be shorter. Omit when using explicit start/end windows; a nonzero value conflicts with those windows.
Recent past calendar days, default 0; 0–92 for this Forecast API. Omit or set 0 with explicit windows. Earlier data use a separate historical endpoint.
Number of future hourly steps, anchored at the current hour or current 15-minute interval rather than midnight. Supply a positive integer; 0 can suppress that component. Available dates and maximum horizon are enforced upstream. Omit or set 0 with explicit start/end windows.
Number of past hourly steps, anchored at the current hour or current 15-minute interval rather than midnight. Supply a positive integer; 0 can suppress that component. Available dates and maximum horizon are enforced upstream. Omit or set 0 with explicit start/end windows.
Number of future 15-minute steps, anchored at the current hour or current 15-minute interval rather than midnight. Supply a positive integer; 0 can suppress that component. Available dates and maximum horizon are enforced upstream. Omit or set 0 with explicit start/end windows.
Number of past 15-minute steps, anchored at the current hour or current 15-minute interval rather than midnight. Supply a positive integer; 0 can suppress that component. Available dates and maximum horizon are enforced upstream. Omit or set 0 with explicit start/end windows.
Optional start hour within the current local day when using forecast_hours, e.g. initial_hours=0 with forecast_hours=12 selects the first 12 hours. Upstream validates the initial-step value.
Optional starting 15-minute step within the current local day when using forecast_minutely_15, e.g. 0 starts at midnight. Upstream validates the initial-step value.
Daily window boundary in YYYY-MM-DD; the end boundary is inclusive. Supply together with end_date. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream.
Daily window boundary in YYYY-MM-DD; the end boundary is inclusive. Supply together with start_date. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream.
Hourly window boundary in YYYY-MM-DDTHH:MM; the end boundary is inclusive. Supply together with end_hour. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream.
Hourly window boundary in YYYY-MM-DDTHH:MM; the end boundary is inclusive. Supply together with start_hour. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream.
15-minute window boundary in YYYY-MM-DDTHH:MM; the end boundary is inclusive. Supply together with end_minutely_15. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream.
15-minute window boundary in YYYY-MM-DDTHH:MM; the end boundary is inclusive. Supply together with start_minutely_15. Repeated windows can be encoded as comma-separated values. Omit nonzero past/forecast length parameters when specifying explicit windows. Only dates available to this Forecast operation are allowed; this does not unlock an unlimited archive. Syntax, ordering, window counts and model availability are checked upstream.
One model identifier or a comma-separated list, e.g. best_match or gfs_seamless,ecmwf_ifs025. Omit for automatic selection. All currently supported Forecast model identifiers are forwarded; no best_match-only restriction. Multiple models add model suffixes to returned variable keys and consume more upstream calls. Deprecated or regional models may be unavailable.
Output timestep for hourly variables: native preserves model resolution; minutely_15/minutely_30 may interpolate; hourly/hourly_1, hourly_3 and hourly_6 select fixed steps.
Temperature unit.
Wind-speed unit; use this current spelling.
Legacy alias for wind_speed_unit. Avoid supplying both: this legacy spelling takes precedence upstream.
Precipitation unit; explicit value takes precedence over length_unit fallback.
Compatibility unit selection. imperial provides an inch precipitation fallback when precipitation_unit is omitted; do not assume every length-valued variable is converted.
ISO 8601 local timestamps or Unix seconds. For daylight-saving-aware times, request unixtime and convert using the returned timezone.
Weather grid-cell preference.
Elevation in metres, comma-separated elevations for multiple locations, or the literal string nan to disable statistical elevation downscaling. With a list, supply one entry per location. Omit to use the digital elevation model.
Solar-panel tilt: numeric 0–90 degrees, or literal string nan for a horizontal tracker. Used by global_tilted_irradiance variables. Range and special value are checked upstream.
Solar-panel azimuth: numeric -180–180 degrees (0 south, -90 east, 90 west), or literal string nan for a vertical tracker. Both tilt and azimuth set to nan select a biaxial tracker. Checked upstream.
Optional comma-separated integer location IDs for multi-location response identification. If supplied, count must match coordinates; one ID can be a single integer string.
Response format. Default json. csv is text; xlsx and flatbuffers are binary and must be handled as bytes by the client. JSON response schema and the retained complete example apply to json only. Subject to 8 MiB response size.
Location metadata layout for CSV/XLSX export: section includes a metadata section; omit excludes it. This does not change JSON forecast variable selection.

Sample response

{
  "current": {
    "interval": 900,
    "temperature_2m": 8.9,
    "time": "2026-11-18T21:30",
    "weather_code": 0
  },
  "current_units": {
    "interval": "seconds",
    "temperature_2m": "°C",
    "time": "iso8601",
    "weather_code": "wmo code"
  },
  "daily": {
    "temperature_2m_max": [
      14.9
    ],
    "temperature_2m_min": [
      7.5
    ],
    "time": [
      "2026-11-18"
    ]
  },
  "daily_units": {
    "temperature_2m_max": "°C",
    "temperature_2m_min": "°C",
    "time": "iso8601"
  },
  "elevation": 3,
  "generationtime_ms": 0.3647804260253906,
  "hourly": {
    "relative_humidity_2m": [
      85,
      85,
      89,
      91,
      92,
      94,
      93,
      92,
      85,
      76,
      67,
      61,
      58,
      57,
      64,
      63,
      64,
      68,
      67,
      63,
      61,
      59,
      58,
      58
    ],
    "temperature_2m": [
      13.3,
      13.2,
      13.1,
      12.5,
      12.4,
      12.1,
      11.6,
      11.4,
      12.1,
      13.1,
      14,
      14.6,
      14.9,
      14.8,
      13.5,
      13.2,
      12.8,
      11.6,
      11.2,
      10.8,
      10,
      9.3,
      8.5,
      7.9
    ],
    "time": [
      "2026-11-18T00:00",
      "2026-11-18T01:00",
      "2026-11-18T02:00",
      "2026-11-18T03:00",
      "2026-11-18T04:00",
      "2026-11-18T05:00",
      "2026-11-18T06:00",
      "2026-11-18T07:00",
      "2026-11-18T08:00",
      "2026-11-18T09:00",
      "2026-11-18T10:00",
      "2026-11-18T11:00",
      "2026-11-18T12:00",
      "2026-11-18T13:00",
      "2026-11-18T14:00",
      "2026-11-18T15:00",
      "2026-11-18T16:00",
      "2026-11-18T17:00",
      "2026-11-18T18:00",
      "2026-11-18T19:00",
      "2026-11-18T20:00",
      "2026-11-18T21:00",
      "2026-11-18T22:00",
      "2026-11-18T23:00"
    ]
  },
  "hourly_units": {
    "relative_humidity_2m": "%",
    "temperature_2m": "°C",
    "time": "iso8601"
  },
  "latitude": 31.247803,
  "longitude": 121.5,
  "timezone": "Asia/Shanghai",
  "timezone_abbreviation": "GMT+8",
  "utc_offset_seconds": 28800
}

Response result

Response structure

Inferred from examples
  • currentobject
    • intervalinteger
    • temperature_2mnumber
    • timestring
    • weather_codeinteger
  • current_unitsobject
    • intervalstring
    • temperature_2mstring
    • timestring
    • weather_codestring
  • dailyobject
    • temperature_2m_maxnumber[]
    • temperature_2m_minnumber[]
    • timestring[]
  • daily_unitsobject
    • temperature_2m_maxstring
    • temperature_2m_minstring
    • timestring
  • elevationinteger
  • generationtime_msnumber
  • hourlyobject
    • relative_humidity_2minteger[]
    • temperature_2mnumber[]
    • timestring[]
  • hourly_unitsobject
    • relative_humidity_2mstring
    • temperature_2mstring
    • timestring
  • latitudenumber
  • longitudenumber
  • timezonestring
  • timezone_abbreviationstring
  • utc_offset_secondsinteger

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Open-Meteo Weather Forecast (Public Test) with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.