/nomads/cities/weather

POST /api/nomads/cities/weather

Price: 20 credits

Get a city's climate by month: felt and real temperature, humidity, most common weather, rain, cloud, air quality, UV index and the estimated number of remote workers there

How to use it

Values are monthly medians over the past few years, one row per calendar month, each with Nomads' own verdict label beside the number.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• city string required — Nomads city alias or city page URL (examples: "bangkok", "bangkok-thailand", "https://nomads.com/chiang-mai"; minLength: 1)

Response

• @type string (default: "NomadsCityWeather")
• alias string required
• name string nullable
• url string required
• months array (default: [])
  • @type string (default: "NomadsWeatherMonth")
  • month integer required
  • month_name string required
  • feels_like_c number nullable
  • feels_like_f number nullable
  • feels_like_label string nullable
  • temperature_c number nullable
  • temperature_f number nullable
  • temperature_label string nullable
  • humidity_percent number nullable
  • humidity_label string nullable
  • weather string nullable
  • rain_mm number nullable
  • rain_label string nullable
  • cloud_percent number nullable
  • cloud_label string nullable
  • air_quality number nullable
  • air_quality_label string nullable
  • uv_index number nullable
  • sun_label string nullable
  • remote_workers_count integer 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 — Nomads does not know the city 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.