/bing/maps/businesses

POST /api/bing/maps/businesses

Price: 10 credits

Get a Bing Maps local business by id: address, coordinates, phone, website, category, opening hours, open status, per-provider ratings with star histograms, review snippets, review highlights and amenities

How to use it

Full profile of one business on Bing Maps. Ratings come per review provider (for example Yelp and Tripadvisor) with up to three review snippets each. Find ids with bing/maps/businesses/search or bing/maps/autocomplete.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• business string required — Bing Maps business id (ypid) or a Bing Maps URL carrying it (examples: "YN6230075ECE10B067", "https://www.bing.com/maps/search?ss=id.ypid%3AYN6230075ECE10B067&cp=47.608906%7E-122.340553&lvl=11"; minLength: 1)

Response

• @type string (default: "BingMapsBusiness")
• id string required
• name string required
• business_type string nullable
• category string nullable
• category_path string nullable
• category_ids array (default: [])
• cuisines array (default: [])
• description string nullable
• address string nullable
• street string nullable
• neighborhood string nullable
• city string nullable
• region string nullable
• postal_code string nullable
• country string nullable
• latitude number nullable
• longitude number nullable
• phone string nullable
• website string nullable
• menu_url string nullable
• social_profiles array (default: [])
• image string nullable
• open_status string nullable
• open_hours_text string nullable
• hours array (default: [])
  • @type string (default: "BingMapsHours")
  • day string required
  • opens string nullable
  • closes string nullable
• timezone string nullable
• is_permanently_closed boolean nullable
• accepts_reservations boolean nullable
• is_claimed boolean (default: false)
• rating number nullable
• rating_count integer nullable
• rating_source string nullable
• provider_ratings array (default: [])
  • @type string (default: "BingMapsProviderRating")
  • provider string required
  • rating number nullable
  • review_count integer nullable
  • url string nullable
  • histogram array (default: [])
    • @type string (default: "BingMapsHistogramBucket")
    • stars integer required
    • percent integer nullable
    • count integer nullable
  • review_topics array (default: [])
• reviews array (default: [])
  • @type string (default: "BingMapsReview")
  • provider string nullable
  • author string nullable
  • rating number nullable
  • text string required
  • published_date string nullable
  • url string nullable
• review_highlights array (default: [])
  • @type string (default: "BingMapsReviewHighlight")
  • text string nullable
  • source string nullable
  • url string nullable
• amenities array (default: [])
• featured_in array (default: [])
  • @type string (default: "BingMapsFeaturedList")
  • url string nullable
  • site string nullable
• bing_url 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 — Business not found 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.