POST /api/brave/maps/search
Price: 20 credits
Brave Maps place search by query, optionally around a point. Returns places with name, coordinates, address, phone, website, opening hours, rating, review count, price range, categories, cuisines and photos.
Brave Maps places for a query. Put a place name in q, or pass latitude and longitude to search around a point; a broad query around a point in a dense city (hotel in central Paris) returns the places within about 1 km.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)q string required — What to look for, optionally with a place name (examples: "coffee seattle"; minLength: 1)count integer required — Maximum number of places to return (min: 1; max: 100)latitude number nullable — Latitude of the search center (examples: 47.6062; min: -90; max: 90)longitude number nullable — Longitude of the search center (examples: -122.3321; min: -180; max: 180)search_lang string — Language of the place data (ISO 639-1) (default: "en"; one of: "en", "az", "id", "ms", "br", "ca", "cs", "cy", "da", "de", "et", "es", "eu", "fr", "gl", "hr", "it", "sw", "lv", "lt", "hu", "nl", "nb", "pl", "pt", "ro", "sq", "sk", "sl", "sr", "fi", "sv", "vi", "tr", "el", "bg", "ru", "uk", "ka", "th", "ko", "zh", "ja")@type string (default: "BravePlace")id string requiredname string (default: "")position integer requiredwebsite_url string nullabledescription string nullablelatitude number nullablelongitude number nullableaddress string nullablephone string nullableopening_hours array (default: [])@type string (default: "BravePlaceHours")day string requiredopens string nullablecloses string nullablerating number nullablebest_rating number nullablereview_count integer nullableis_tripadvisor_rating boolean nullableprice_range string nullablecategory string nullablecategories array (default: [])icon_category string nullablecuisines array (default: [])thumbnail string nullableimages array (default: [])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 — The entity was not found, or a precondition failed 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.