Delete Review Reply API
The Delete Review Reply API removes the business owner reply from a Google Business Profile review. It uses DELETE /v1/reviews/{reviewId}/reply, with the review identified in the path and the platform and integration account supplied as query parameters. Deleting a reply is free.
Delete Review Reply API — operation summary with exact method and path
Use this operation when a business owner reply needs to be removed from a Google Business Profile review. The request targets a single review through reviewId in the path. The platform query parameter must be googlebusiness, the only supported value documented for this operation. The accountId query parameter carries the integration ID for the connected account that owns the review context. Before sending the request, confirm that reviewId identifies the intended review, that platform is set to googlebusiness, that accountId is the correct integration ID, and that the access key is ready for the x-access-key header. If any of those values is missing or mismatched, stop and correct it before calling the endpoint, because the request cannot identify the correct review and account without them.
Authorization: x-access-key header with <token>
Authorization uses the accessKey scheme in the x-access-key header. Send the token as the header value in the form x-access-key: <token>. Place the header on the DELETE request itself; do not put the token in the path or in a query parameter. If the header is absent or invalid, expect the request to be rejected rather than processed, and check the header name and value before retrying.
Path and query parameters
The input contract table below maps each parameter to its location, type, requiredness, and constraint. The path parameter reviewId is a required string and forms part of the endpoint path. The query parameters platform and accountId are both required strings. The platform value is constrained to googlebusiness, and accountId is the integration ID. Keep the parameter names exactly as shown, including their case, when building the request URL.
Worked request example with {{API_BASE_URL}}
The worked request example below shows the exact method, path, and query parameters with the origin replaced by the modular base URL placeholder. Replace the placeholder reviewId value in the path with the actual review identifier, keep platform=googlebusiness, and replace the placeholder accountId value with the integration ID. Add the x-access-key header with your token. After sending the request, check the response body for the success and message fields described below rather than relying only on the status code.
Response body and status-code matrix
Every documented status code returns a JSON body with the same shape: a required boolean success field and a required string message field. The status-code matrix below lists only the codes supplied in the source and marks per-code error semantics as unspecified, because distinct error messages and meanings were not provided for each code. Treat the message field as the human-readable detail returned with the response, and do not assume a specific error meaning for a code beyond its numeric value. When a call fails, record the status code together with the returned success and message values so the failure can be diagnosed from the actual response.
Caller checklist and unspecified error semantics
Run through a short pre-flight checklist before each deletion. Confirm the reviewId in the path, confirm platform is googlebusiness, confirm accountId is the integration ID, and confirm the x-access-key header carries the token. Then send the DELETE request and inspect the response body for success and message. If the response indicates failure, use the returned message and status code to decide whether to correct an input value, check authorization, or retry later, without assuming an error meaning that the documented contract does not specify.
| Parameter | Location | Type | Required | Constraint / notes |
|---|---|---|---|---|
| reviewId | path | string | true | Identifies the review in /v1/reviews/{reviewId}/reply |
| platform | query | string | true | Value in "googlebusiness"; platform the review lives on, only googlebusiness today |
| accountId | query | string | true | Integration ID passed as accountId |
Exact source contract; per-status error semantics unspecified in source.
| Status code | Content type | Response shape | Per-code semantics |
|---|---|---|---|
| 200 | application/json | success: boolean (required), message: string (required) | Unspecified in source |
| 400 | application/json | success: boolean (required), message: string (required) | Unspecified in source |
| 401 | application/json | success: boolean (required), message: string (required) | Unspecified in source |
| 403 | application/json | success: boolean (required), message: string (required) | Unspecified in source |
| 404 | application/json | success: boolean (required), message: string (required) | Unspecified in source |
| 429 | application/json | success: boolean (required), message: string (required) | Unspecified in source |
| 502 | application/json | success: boolean (required), message: string (required) | Unspecified in source |
Exact source contract; per-status error semantics unspecified in source.
curl -X DELETE "{{API_BASE_URL}}/v1/reviews/string/reply?platform=googlebusiness&accountId=string" -H "x-access-key: <token>"{
"success": true,
"message": "string"
}| Scope | Field | Type | Type reference | Required | Description | Constraints |
|---|---|---|---|---|---|---|
| reviewId#1 | reviewId | string | __0 | Yes | ||
| platform#2 | platform | string | __0 | Yes | Platform the review lives on. Only googlebusiness today. | kind: schemaValueIn; value: "googlebusiness" |
| accountId#3 | accountId | string | __0 | Yes | ||
| response#4 | response | object | __0 | |||
| response#4 | response.success | boolean | __1 | Yes | ||
| response#4 | response.message | string | __2 | Yes |