Skip to main content
This section documents the map entries data returned by the Microsoft Copilot endpoint. Map entries are part of the Copilot response, so no separate API call is needed. For use cases, pricing context, and copy-paste examples, see the Copilot shopping API page on the product site — it documents map entries alongside shopping cards.

Example request

Map entries are returned by default when Copilot surfaces local business data. No flag is required.
This produces a response containing the map array documented below.

Overview

Map entries are auto-extracted from Copilot’s local entity data (primarily Google). No additional parameters are required. Map entries are included by default when available in the response.
Map entries in Copilot

Map entry structure

Each map entry contains business information using Copilot’s native structure:

Location object

Review object

Photo object

Example usage

Response with map entries:
All fields are optionalExcept for name and position, all fields in map entries are optional. Use optional chaining (?.) or check for field existence before accessing. Field availability depends on what data is available for each business.