/bing/maps/businesses/search

POST /api/bing/maps/businesses/search

Price: 20 credits

Search local businesses on Bing Maps by text and place, optionally filtered by minimum star rating and opening hours

How to use it

Put the place inside the query text, for example coffee shops in seattle. Each result carries its id for bing/maps/businesses and bing/maps/businesses/photos.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — What to look for and where (examples: "coffee shops in seattle", "dentist near 10001", "pizza"; minLength: 1)
• count integer required — Max number of results (min: 1; max: 50)
• min_rating string nullable — Minimum star rating (one of: "2+", "3+", "4+")
• hours string nullable — Opening hours condition (one of: "open_24_hours", "late_night")

Response

• @type string (default: "BingMapsBusinessCard")
• id string required
• name string required
• category string nullable
• category_path string nullable
• address string nullable
• latitude number nullable
• longitude number nullable
• phone string nullable
• website string nullable
• rating number nullable
• rating_count integer nullable
• rating_source string nullable
• open_status string nullable
• open_hours_text string nullable
• image string nullable

Errors

• 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.