/nomads/cities/cost_of_living

POST /api/nomads/cities/cost_of_living

Price: 20 credits

Get a city's cost of living: monthly cost for a nomad, expat, local and family, hotel, Airbnb and rent prices, coworking, meals, drinks, school, mobile data, taxi and, where Nomads lists it, the estimated tax on a $50k, $100k and $250k income

How to use it

Every item carries its price in US dollars in price_usd; period says whether the price is per month, night, year or trip and is null on one-off amounts such as meals, the median home price and the tax_on_50k, tax_on_100k and tax_on_250k estimates, whose price_usd is the tax on that income. local_price is the same price in local_currency, and both are null on items for which Nomads gives no local price for that same quantity, such as mobile data and taxi, and the median home price outside US-dollar cities.

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: "NomadsCityCostOfLiving")
• alias string required
• name string nullable
• url string required
• costs array (default: [])
  • @type string (default: "NomadsCostItem")
  • key string required
  • label string required
  • description string nullable
  • price_usd number nullable
  • price_text string nullable
  • period string nullable
  • local_price number nullable
  • local_currency 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 — 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.