Address search
Use Geocoding endpoints to turn address search into repeatable API requests with documented inputs and JSON responses.
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.
Endpoint families
3
Documented params
28
Examples
3
Live catalog snapshot
Active endpoints
3
Methods
GET
Required params
6
Schema refs
3
{
"platform": "Geocoding",
"endpoint": "geocoding-search",
"method": "GET",
"path": "/geocoding/search",
"auth": "apiKey"
}Related use cases
Use cases
Search addresses, reverse geocode coordinates, and look up Nominatim OSM identifiers through documented Crawlora API endpoints.
Use Geocoding endpoints to turn address search into repeatable API requests with documented inputs and JSON responses.
Use Geocoding endpoints to turn reverse geocoding into repeatable API requests with documented inputs and JSON responses.
Use Geocoding endpoints to turn location enrichment into repeatable API requests with documented inputs and JSON responses.
Managed execution
Each Crawlora platform API is designed around a specific data surface. Instead of exposing a generic fetch endpoint, Crawlora combines endpoint-specific request logic, managed infrastructure, parsing, normalization, billing, and Playground-tested examples.
Request behavior is tuned for the target platform and endpoint type.
Supported endpoints can use managed proxy routing to improve reliability and reduce infrastructure work.
Dynamic pages can be routed through managed browser instances where JavaScript rendering is required.
Challenge pages and unusable upstream responses are detected and surfaced clearly.
Results are returned as documented JSON instead of raw HTML.
Test the same route from Docs and Playground before production integration.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/geocoding/lookup
/geocoding/reverse
/geocoding/search
Endpoint catalog
/geocoding/searchReturns typed Nominatim JSONv2 forward geocoding results. Use either q or structured fields, not both.
/geocoding/reverseReturns the nearest typed Nominatim JSONv2 place for latitude and longitude.
/geocoding/lookupReturns typed Nominatim JSONv2 places for comma-separated OSM ids such as W34633854,N123,R456.
Related 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.
How to scrape 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.