/nomads/cities

POST /api/nomads/cities

Price: 20 credits

Get a Nomads.com city: nomad score and rank, the full score table, cost of living for a nomad, expat, local and family, internet speed, current weather and air quality, member counts and location

How to use it

Pass the city alias from a Nomads URL or from nomads/cities/search. Guide facts, cost items, reviews, weather, trends, visitor nationalities and related cities each have their own nomads/cities endpoint.

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: "NomadsCity")
• alias string required
• long_alias string nullable
• url string nullable
• name string required
• country string nullable
• country_code string nullable
• country_alias string nullable
• region string nullable
• state string nullable
• state_code string nullable
• latitude number nullable
• longitude number nullable
• population integer nullable
• rank integer nullable
• nomad_score number nullable
• cost_score number nullable
• internet_score number nullable
• likes_score number nullable
• safety_score number nullable
• air_quality_score number nullable
• air_quality_now_score number nullable
• internet_speed_mbps number nullable
• air_quality number nullable
• air_quality_now number nullable
• humidity_percent number nullable
• ac_prevalence_percent number nullable
• temperature_c number nullable
• temperature_f number nullable
• feels_like_c number nullable
• feels_like_f number nullable
• weather_icon string nullable
• weather_emoji string nullable
• cost_for_nomad_usd number nullable
• cost_for_expat_usd number nullable
• cost_for_local_usd number nullable
• cost_for_family_usd number nullable
• members_here_count integer nullable
• members_here_estimated_count integer nullable
• members_been_count integer nullable
• members_been_estimated_count integer nullable
• trips_growth_2y_percent number nullable
• image string nullable
• image_updated_at integer nullable
• video_thumbnail string nullable
• name_chinese string nullable
• country_chinese string nullable
• state_chinese string nullable
• id string required
• description string nullable
• review_count integer nullable
• likes_count integer nullable
• dislikes_count integer nullable
• scores_updated_at integer nullable
• review_keywords array (default: [])
• scores array (default: [])
  • @type string (default: "NomadsScore")
  • key string required
  • label string required
  • value string nullable
  • rating integer nullable
  • score number nullable
  • level_percent number nullable
  • is_country_level boolean (default: false)

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.