/osm/geocode/reverse

POST /api/osm/geocode/reverse

Price: 1 credit

Reverse geocoding: resolve a latitude/longitude pair to the nearest OpenStreetMap place and address

How to use it

Reverse-geocode a coordinate. Provide lat and lon; returns the nearest place with a structured address, category/type, and extra tags. Use zoom to control address granularity (18=building, 10=city, 5=state).

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 (examples: 48.8584; min: -90; max: 90)
• lon number required — Longitude (examples: 2.2945; min: -180; max: 180)
• zoom integer nullable — Address detail level, 0 (country) to 18 (building) (min: 0; max: 18)
• layer array nullable — Restrict result to one or more data layers (one of: "address", "poi", "railway", "natural", "manmade")
• address_details boolean — Include a structured address breakdown (default: true)
• extra_tags boolean — Include additional OSM tags (website, phone, opening hours…) (default: true)
• name_details boolean — Include the full set of name/label variants (default: true)
• polygon_geojson boolean — Include the object geometry as a GeoJSON object (default: false)
• accept_language string nullable — Preferred language(s) for names and labels (examples: "en", "de,en")

Response

• @type string (default: "OsmPlace")
• place_id integer nullable
• osm_type string nullable
• osm_id integer nullable
• latitude number nullable
• longitude number nullable
• category string nullable
• place_type string nullable
• place_rank integer nullable
• importance number nullable
• addresstype string nullable
• name string nullable
• display_name string nullable
• address object nullable
  • @type string (default: "OsmAddress")
  • house_number string nullable
  • road string nullable
  • quarter string nullable
  • neighbourhood string nullable
  • suburb string nullable
  • borough string nullable
  • city_district string nullable
  • city string nullable
  • municipality string nullable
  • county string nullable
  • state_district string nullable
  • state string nullable
  • region string nullable
  • postcode string nullable
  • country string nullable
  • country_code string nullable
  • iso3166_2 string nullable
• extratags object (default: {})
• namedetails object (default: {})
• boundingbox array (default: [])
• geojson object nullable
• source_url 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 place found at the given coordinates 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.