Disconnect listings from locations

Removes the link between a listingsAPI location and the publisher listing (Google Business Profile or Facebook Page) it is currently connected to. After disconnection, listingsAPI stops pushing updates to that listing for the affected locations. The location itself remains in your account — only the listing link is severed.

Pass one or more base64-encoded location IDs in locationIds; the call is a bulk operation, so you can disconnect a batch in a single request. The deleted count in the response tells you how many location–listing links were actually removed (locations with no connected listing are simply skipped).

Use case — re-point a location to a different account. When a customer moves a storefront from one Google account to another, first disconnect the location's current listing here, then use trigger-matches and connect-listing on the new connected account to link it to the correct listing.

Use case — offboard without deleting. When a customer downgrades and no longer wants listingsAPI managing their Google/Facebook presence but wants to keep the location record and its listingsAPI-hosted data, disconnect the listing rather than archiving the location. This stops outbound syncing while preserving the location for other publishers.

This endpoint mutates a live connection and pushes state to Google/Facebook. The request shape and sample response above are documented from the API specification; the call is not executed against production data.