Address search
Mit Geocoding-Endpunkten verwandelst du address search in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Normalize location search, coordinate lookup, and OSM identifier enrichment through API-key protected geocoding endpoints.
Search addresses, reverse geocode coordinates, and look up Nominatim OSM identifiers through documented Crawlora API endpoints.
Endpunkt-Familien
3
Dokumentierte Parameter
28
Beispiele
3
Live-Katalog-Snapshot
Aktive Endpunkte
3
Methoden
GET
Pflichtparameter
6
Schema-Referenzen
3
{
"platform": "Geocoding",
"endpoint": "geocoding-search",
"method": "GET",
"path": "/geocoding/search",
"auth": "apiKey"
}Verwandte Use Cases
Use Cases
Search addresses, reverse geocode coordinates, and look up Nominatim OSM identifiers through documented Crawlora API endpoints.
Mit Geocoding-Endpunkten verwandelst du address search in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Geocoding-Endpunkten verwandelst du reverse geocoding in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Geocoding-Endpunkten verwandelst du location enrichment in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Geocoding-Endpunktkatalog — 3 Endpunkte, 28 dokumentierte Request-Parameter und 3 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
3 documented Geocoding endpoints, grouped into 3 request families — Lookup, Reverse and Search.
28 request parameters are documented across those Geocoding endpoints, 6 of them required — the full input contract is public before you write any integration code.
3 of the 3 Geocoding endpoints ship a recorded example response, and 3 carry a documented response schema — you can code against the real JSON before the first request.
Geocoding endpoints document their error responses (400, 404, 502 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
3 hosted MCP tools back the Geocoding endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
Diese Karten werden aus dem aktiven Endpunktkatalog generiert, damit die Landingpage dieselbe API-Oberfläche widerspiegelt, die auch Docs und Playground nutzen.
/geocoding/lookup
/geocoding/reverse
/geocoding/search
Endpunktkatalog
/geocoding/searchReturns typed Nominatim JSONv2 forward geocoding results. Use either q or structured fields, not both.
Hinweise zur Response
Example response: ```json {"code":200,"msg":"OK","data":{"query":"Empire State Building","results":[{"place_id":358220252,"osm_type":"way","osm_id":34633854,"lat":"40.7484421","lon":"-73.9856589","category":"office","type":"yes","place_rank":30,"importance":0.5803438355141769,"addresstype":"office","name":"Empire State Building","display_name":"Empire State Building, 350, 5th Avenue, New York, United States","address":{"office":"Empire State Building","house_number":"350","road":"5th Avenue","city":"New York","state":"New York","postcode":"10118","country":"United States","country_code":"us"},"boundingbox":["40.7479255","40.7489585","-73.9865012","-73.9848166"]}]}} ```
MCP-Tool geocoding_search
/geocoding/reverseReturns the nearest typed Nominatim JSONv2 place for latitude and longitude.
Hinweise zur Response
Example response: ```json {"code":200,"msg":"OK","data":{"place_id":359125914,"osm_type":"node","osm_id":13306330095,"lat":"40.7484257","lon":"-73.9856700","category":"tourism","type":"viewpoint","place_rank":30,"importance":0.00009175936522464359,"addresstype":"tourism","name":"","display_name":"350, 5th Avenue, Koreatown, Manhattan, New York, 10118, United States","address":{"house_number":"350","road":"5th Avenue","neighbourhood":"Koreatown","suburb":"Manhattan","city":"New York","state":"New York","postcode":"10118","country":"United States","country_code":"us"},"boundingbox":["40.7483757","40.7484757","-73.9857200","-73.9856200"]}} ```
MCP-Tool geocoding_reverse
/geocoding/lookupReturns typed Nominatim JSONv2 places for comma-separated OSM ids such as W34633854,N123,R456.
Hinweise zur Response
Example response: ```json {"code":200,"msg":"OK","data":{"query":"W34633854","results":[{"place_id":358220252,"osm_type":"way","osm_id":34633854,"lat":"40.7484421","lon":"-73.9856589","category":"office","type":"yes","place_rank":30,"importance":0.5803438355141769,"addresstype":"office","name":"Empire State Building","display_name":"Empire State Building, 350, 5th Avenue, New York, United States","address":{"office":"Empire State Building","house_number":"350","road":"5th Avenue","city":"New York","state":"New York","postcode":"10118","country":"United States","country_code":"us"},"extratags":{"website":"https://www.esbnyc.com","wikidata":"Q9188"},"namedetails":{"name":"Empire State Building","name:en":"Empire State Building"}}]}} ```
MCP-Tool geocoding_lookup
Verwandte APIs
Maps & Local Data
Collect local business and place data from Google Maps for location intelligence workflows.
Maps & Local Data
Search ready-made scraped datasets for local business research with filters, facets, geo queries, and repeatable API output.
Maps & Local Data
Compare cities and countries with normalized Numbeo cost-of-living and quality indices. Retrieve city or country detail and current or historical rankings for location research, relocation products, market analysis, and local-data enrichment.
So scrapst du Geocoding
Geocoding turns an address into coordinates and coordinates back into an address. Crawlora's 3 geocoding endpoints wrap Nominatim's typed JSONv2 responses — forward search, reverse lookup, and OpenStreetMap identifier resolution — behind one API key.
Pass a free-text q, or the structured street, city, county, state, country, and postalcode fields — use one form or the other, not both in the same call.
Send lat and lon to get the nearest matching place, with zoom controlling how coarse or fine the returned address is.
Pass osm_ids to look up known nodes, ways, or relations directly instead of searching for them again.
addressdetails, extratags, and namedetails add the structured address breakdown, the extra OSM tags, and alternate-language names; countrycodes and accept_language narrow and localize the results.
FAQ
OpenStreetMap, via Nominatim. Responses are typed JSONv2, so you get the same place, address, and bounding-box structure Nominatim returns, normalized and behind a single Crawlora key.
No. Use either the free-text q parameter or the structured street, city, county, state, country, and postalcode fields in a single call. Mixing them is not supported and will not narrow the search the way you expect.
Set accept_language for the response language and namedetails to include the place's alternate names. extratags adds the extra OpenStreetMap tags that are not part of the default response.
Nominatim is a shared community service with its own usage policy, and upstream capacity problems surface as 5xx responses rather than bad data. Design for occasional upstream unavailability and retry rather than assuming every call succeeds.