Get Bing analytics for a location — Listings API

Parameters

Path

Name	Type	Required	Description
locationId	string	required	Location ID, either the Base64 Relay id (e.g. TG9jYXRpb246MTgwMDI4OQ==) or the raw numeric database id (e.g. 1800289). Both forms resolve to the same location.

Query

Name	Type	Required	Description	Default
fromDate	string	optional	Start of the range (YYYY-MM-DD). Defaults to a recent window when omitted.	—
toDate	string	optional	End of the range (YYYY-MM-DD).	—

Responses

200Weekly Bing view metrics. `views` is a time-series array; it is empty when no data exists for the range or the Bing profile is not connected.

Response

{  "data": {    "bingInsights": {      "views": [        { "startTime": "2025-06-02T00:00:00+00:00", "value": 73 },        { "startTime": "2025-06-09T00:00:00+00:00", "value": 58 }      ]    }  }}

401Unauthenticated, missing or invalid API key.

Returns Bing Places profile view data for a location. Bing analytics are bucketed weekly, each point in views represents one week's view count starting at startTime. Data is refreshed every Monday for the preceding week, so the most recent complete week is what you will see.

Either id form works in the path

bing-analytics takes the Base64 Relay id (TG9jYXRpb246MTgwMDI4OQ==) or the raw numeric id (1800289), and both resolve to the same location. Prefer the Relay id, which is what the read endpoints return. A value that is neither returns {"data":{"bingInsights":null},"errors":[...]} with a 200 status rather than the metrics object.

Shell

curl -s 'https://listingsapi.com/api/v4/locations/TG9jYXRpb246MTgwMDI4OQ==/bing-analytics?fromDate=2025-01-01&toDate=2025-12-31' \  -H "Authorization: API $LISTINGSAPI_KEY"

Tracking Bing visibility trends

Because Bing reports one value per week, this endpoint is best for a trend line rather than day-level attribution: fetch a multi-month range and plot views to see whether listing visibility on Bing is climbing or slipping. When the location has no Bing data for the window (or its Bing profile is not connected) the endpoint still returns 200 with views as an empty array ([]), treat that as "no data" rather than an error. Combine with Google and Facebook analytics for a full multi-publisher dashboard.