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
Start building