Google — disconnect review site

Overview

Disconnect a Google Business Profile location from a store review site: clears the token/location, sets sendto_scrapper=N, connection_status=disconnected, disconnect_reason=MANUAL, clears the company googleapi_access_token, logs the change, emails the account owner (ACCOUNT_DISCONNECTED), and records a DISCONNECTED_MANUAL gbp event. Emits audit STORE_REVIEW_SITE_OAUTH_DISCONNECTED.

Prerequisites

  • Either a bearer token in the Authorization header, or the invite hash this endpoint accepts in place of one.
  • Values for the required query parameter store_review_site_id — see the table below.

Base URL

EnvironmentURL
Productionhttps://production-api.shoutaboutus.com
Developmenthttps://development-api.shoutaboutus.com

Endpoint

GET /api/v1/google/review-site/disconnect

Authentication

  • A bearer token is optional here. Send one to act as a signed-in user, or supply the documented hash instead.

  • Use a bearer token (scoped by an ownership check).

  • OR use an invite hash (no token) whose encoded store must own store_review_site_id.

Rate limit

  • 30 requests/min per IP (public).

Query parameters

FieldTypeRequiredDescription
store_review_site_idintegerRequiredThe store review site to disconnect.
hashstringOptionalInvite hash encoding the store_id; grants access without a token.

How it works

  • 200 on disconnect. 422 if store_review_site_id does not exist.

Response

200 OK · 200

{
  "data": {
    "status": "success",
    "message": "The review site has been disconnected!"
  }
}

422 Validation error · 422

{
  "message": "The selected store review site id is invalid.",
  "errors": {
    "store_review_site_id": [
      "The selected store review site id is invalid."
    ]
  }
}

Errors

StatusMeaning
401The bearer token is missing, expired or invalid
422Validation error
500Unexpected server error

Example request

curl --request GET \
  --url "https://production-api.shoutaboutus.com/api/v1/google/review-site/disconnect?store_review_site_id=123" \
  --header 'Authorization: Bearer <bearer-token>' \
  --header 'Accept: application/json'

Did this page help you?