/api/v4/connected-accounts/disconnect-listingDisconnect a listing from a location
Unlinks the connected publisher listing from a single Listings API location.
Parameters
Body
| Name | Type | Required | Description |
|---|---|---|---|
| input | object | required | Wrapper object. The entire request body must be nested under `input`. |
| input.locationId | string | required | Base64-encoded Relay ID of the one location to disconnect. |
| input.site | string | optional | Publisher to disconnect from: `GOOGLE`, `FACEBOOK`, or `APPLE`. Required unless you send `providerId`. |
| input.providerId | string | optional | The publisher's own account identifier, as an alternative to `site`. Required unless you send `site`. |
Sample request
Ready-to-paste body. Replace placeholder IDs and values with yours.
{ "input": { "locationId": "TG9jYXRpb246MTgwMDI4OQ==", "site": "GOOGLE" }}Responses
200Listing disconnected.
{ "data": { "disconnectConnectedAccountsLocations": { "clientMutationId": null, "success": true, "errors": null } }}401Unauthenticated, missing or invalid API key.
Removes the link between a Listings API location and the publisher listing (Google Business Profile, Facebook Page, or Apple Business Connect) it is currently connected to. After disconnection, Listings API stops pushing updates to that listing. The location itself remains in your account, only the listing link is severed.
Request shape. The body must be wrapped in an input object carrying a single locationId, plus either site (GOOGLE, FACEBOOK, or APPLE) or providerId to say which connection to sever. This is not a bulk endpoint: one location per call, so loop if you need several.
Sending neither site nor providerId returns SY10056 ("Site is not valid for the location disconnection"). A location that has no active connection for that site returns SY10057 ("Location is not connected for the site") rather than a silent success, so a success: true really does mean a link was removed.
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 with site: "GOOGLE", 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 Listings API managing their Google/Facebook presence but wants to keep the location record and its Listings API-hosted data, disconnect the listing rather than archiving the location. This stops outbound syncing while preserving the location for other publishers.
This endpoint changes a live connection and pushes the change to the publisher. The sample request and response above are examples.
curl -X POST 'https://listingsapi.com/api/v4/connected-accounts/disconnect-listing' \ -H "Authorization: API $LISTINGSAPI_KEY" \ -H 'Content-Type: application/json' \ -d '{ "input": { "locationId": "TG9jYXRpb246MTgwMDI4OQ==", "site": "GOOGLE" } }'