Crawlora Docs
Collect local business search results, enrich each website for public emails, deduplicate records, and export compliant business research.
Collect local business search results, enrich each website for public emails, deduplicate records, and export compliant business research.
Only endpoints that exist in the generated endpoint metadata are linked here. Missing optional endpoints are intentionally omitted.
/google/map/searchSearches Google Maps with a request body of `keyword` (required) plus optional `language` (default `en`) and `country` (an ISO-2 code such as `us`, default `us`). Each place has its name, place id, categories, address, coordinates, phone, website, rating and review count. `rating` is `null` when Google has no aggregate rating.
/google/map/place/{place_id}Returns the Google Maps details of one place by its Google `place_id`: name, categories, address, coordinates, phone, website, description, image, amenities, rating and review count. `rating` is `null` when the place has no aggregate rating on Google.
/geocoding/searchSearches OpenStreetMap places by address. Pass either free-text `q` or structured fields (`street`, `city`, `county`, `state`, `country`, `postalcode`), not both. `limit` defaults to 10 and is clamped to 20; `countrycodes` restricts by ISO 3166-1 alpha-2 country. Each result has its display name, coordinates, category, type, bounding box, importance and address parts. No match returns `404`.
/geocoding/reverseReturns the nearest OpenStreetMap place for the required `lat` and `lon`. `zoom` (0 to 18, default 18) sets the level of detail; `addressdetails` defaults to true, and `extratags`, `namedetails` and `accept_language` are optional. The place has its display name, category and type, OSM type and id, bounding box, importance and address parts. Out-of-range coordinates return `400`; no place found returns `404`.
| Field | Notes |
|---|---|
| query | Workflow field; map to exact endpoint response fields from endpoint docs. |
| location | Workflow field; map to exact endpoint response fields from endpoint docs. |
| place_id | Workflow field; map to exact endpoint response fields from endpoint docs. |
| osm_id | Workflow field; map to exact endpoint response fields from endpoint docs. |
| lat | Workflow field; map to exact endpoint response fields from endpoint docs. |
| lon | Workflow field; map to exact endpoint response fields from endpoint docs. |
| name | Workflow field; map to exact endpoint response fields from endpoint docs. |
| address | Workflow field; map to exact endpoint response fields from endpoint docs. |
| category | Workflow field; map to exact endpoint response fields from endpoint docs. |
| rating | Workflow field; map to exact endpoint response fields from endpoint docs. |
| phone | Workflow field; map to exact endpoint response fields from endpoint docs. |
| website | Workflow field; map to exact endpoint response fields from endpoint docs. |
| Workflow field; map to exact endpoint response fields from endpoint docs. | |
| email_status | Workflow field; map to exact endpoint response fields from endpoint docs. |
| socials | Workflow field; map to exact endpoint response fields from endpoint docs. |
| checked_at | Workflow field; map to exact endpoint response fields from endpoint docs. |
This example uses the real Google Maps search API endpoint. Exact request fields come from the endpoint metadata.
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X POST "https://api.crawlora.net/api/v1/google/map/search" \
-H "x-api-key: $CRAWLORA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"country":"us","keyword":"hotel san francisco","language":"en"}'Use endpoint detail pages for exact response schemas. This recipe does not invent response fields.
{
"code": 200,
"msg": "OK",
"data": [
{
"url": "https://www.google.com/maps/place/?q=place_id:ChIJs3cv0KuvEmsRHcXYwNJ6GU0",
"name": "Primi Italian",
"place_id": "ChIJs3cv0KuvEmsRHcXYwNJ6GU0",
"category": [
"italian_restaurant"
],
"address": "168 Clarence St, Sydney NSW 2000, Australia",
"latitude": -33.8701437,
"longitude": 151.2056158,
"rating": 4.1,
"review_count": 3213
}
]
}Use place_id as the stable dedupe key when available and keep snapshot timestamps for repeated market mapping.
Estimate usage by multiplying requests by endpoint credit cost. The table below only shows real credit costs available from the billing constants.
| Endpoint | Credit cost | Docs |
|---|---|---|
| Google Maps search API | 5 credits/request | /docs/google-map/google-map-search |
| Google Maps place details API | 5 credits/request | /docs/google-map/google-map-place |
| Search Nominatim places | 1 credit/request | /docs/geocoding/geocoding-search |
| Reverse geocode coordinates | 1 credit/request | /docs/geocoding/geocoding-reverse |
Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.
Read Crawlora termsUse this recipe for workflow shape, then rely on endpoint reference pages for exact paths, request schemas, response schemas, and credit costs.