Listings APIListings API
Get API keySign in
POST/api/v4/locations/reviews/respond/archive

Archive a response

Archives an existing owner response, removing it from the active responses tracked for an interaction.

Requires an API key. See Authentication for header format and key rotation.

Parameters

Body

NameTypeRequiredDescription
responseIdstringrequiredID of the response to archive (the `id` from an interaction's `responses` array).

Sample request

Ready-to-paste body. Replace placeholder IDs and values with yours.

{
  "responseId": "2090753a-ece6-4837-8336-8494ad308523"
}

Responses

200Response archived. `data.archiveReviewResponse.status` is `"true"` on success.
{
  "data": {
    "archiveReviewResponse": {
      "status": "true",
      "errors": null
    }
  }
}
401Unauthenticated — missing or invalid API key.

Archives a previously posted response to an interaction. Archiving is a soft-delete from Listings API's local cache — it removes the response from the tracked responses for the interaction but does not retract it from the source platform. Replies already published on Google, Yelp, or Facebook remain live there.

Obtain the responseId from an interaction's responses[].id via Get interactions by IDs or List interactions.

Use case: clearing a superseded draft reply

If a reply was created in error or superseded before it published, archive it to keep the interaction's responses list clean and its responded flag accurate in your dashboard:

{
  "responseId": "2090753a-ece6-4837-8336-8494ad308523"
}

To change the wording of a reply that has already gone live on the source site, use Edit a response instead — archiving will not remove it from the publisher.

curl -X POST 'https://listingsapi.com/api/v4/locations/reviews/respond/archive' \
  -H "Authorization: API $LISTINGSAPI_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "responseId": "<responseId>"
  }'
Run in playground