/numbeo/cities/crime

POST /api/numbeo/cities/crime

Price: 5 credits

Get a city's crime and safety indices with the survey scores behind them: level of crime, specific worries, problem areas and safety walking alone by day and night

How to use it

Pass the alias from a Numbeo city URL or the numeric id from numbeo/cities/search. A city with too few contributors returns its identity and nearby cities with the indices empty, so do not read empty indices as zero.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• city string required — City alias, numeric Numbeo city id or Numbeo city page URL (examples: "Berlin", "London-Canada", "5439", "https://www.numbeo.com/crime/in/New-York"; minLength: 1)

Response

• @type string (default: "NumbeoCityCrime")
• id string required
• alias string nullable
• url string nullable
• name string required
• country string nullable
• nearby_cities array (default: [])
  • @type string (default: "NumbeoNearbyCity")
  • name string required
  • alias string nullable
  • url string nullable
  • distance_km number nullable
• crime_index number nullable
• safety_index number nullable
• components array (default: [])
  • @type string (default: "NumbeoComponent")
  • key string nullable
  • name string required
  • value number nullable
  • level string nullable
• contributor_count integer nullable
• updated_date 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 — No Numbeo city matches the alias, id or URL 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.