/openweathermap/forecast/hourly

POST /api/openweathermap/forecast/hourly

Price: 1 credit

Get an extended 3-hourly weather forecast for a geographic point

How to use it

Get an extended 3-hourly weather forecast for a point by latitude and longitude. Returns the resolved city (name, country, coordinates, population, timezone offset, sunrise/sunset) and a list of forecast records; each record covers a 3-hour window with temperature, feels-like, min/max, pressure, sea/ground-level pressure, humidity, dew point, clouds, wind, visibility, precipitation probability, and conditions. Use 'count' to set how many 3-hour steps to return (up to about 16 days ahead) and 'units' for the measurement system. Timestamps are unix seconds plus a human-readable UTC text field.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• lat number required — Latitude in WGS84 coordinates (examples: 40.71; min: -90; max: 90)
• lon number required — Longitude in WGS84 coordinates (examples: -74.01; min: -180; max: 180)
• units string — Measurement system: metric (Celsius, m/s), imperial (Fahrenheit, mph), standard (Kelvin) (default: "metric"; one of: "metric", "imperial", "standard")
• count integer required — Max number of 3-hour forecast steps to return (min: 1; max: 384)

Response

• @type string (default: "OpenweathermapForecastHourly")
• city object nullable
  • @type string (default: "OpenweathermapCity")
  • id integer nullable
  • name string nullable
  • country string nullable
  • lat number nullable
  • lon number nullable
  • population integer nullable
  • timezone integer nullable
  • sunrise integer nullable
  • sunset integer nullable
• records array (default: [])
  • @type string (default: "OpenweathermapForecastRecord")
  • forecast_at integer nullable
  • forecast_at_text string nullable
  • temp number nullable
  • feels_like number nullable
  • temp_min number nullable
  • temp_max number nullable
  • pressure number nullable
  • sea_level number nullable
  • grnd_level number nullable
  • humidity number nullable
  • dew_point number nullable
  • clouds number nullable
  • wind_speed number nullable
  • wind_deg number nullable
  • wind_gust number nullable
  • visibility number nullable
  • pop number nullable
  • part_of_day string nullable
  • rain_3h number nullable
  • snow_3h number nullable
  • conditions array (default: [])
    • @type string (default: "OpenweathermapCondition")
    • id integer nullable
    • main string nullable
    • description string nullable
    • icon string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.