Removes the specified hold and releases the accounts or organizational unit covered by the hold. If the data is not preserved by another hold or retention rule, it might be purged.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-02-05 UTC."],[[["Removes a specified hold, potentially leading to data purging if not preserved by other means."],["Uses an HTTP DELETE request with matter and hold IDs as path parameters."],["Requires an empty request body and returns an empty response body upon success."],["Needs authorization with the `https://www.googleapis.com/auth/ediscovery` scope."]]],["This document outlines the process for removing a hold on accounts or organizational units. The core action is a `DELETE` HTTP request to `https://vault.googleapis.com/v1/matters/{matterId}/holds/{holdId}`, utilizing gRPC Transcoding. It requires two path parameters: `matterId` and `holdId`. The request body must be empty, and a successful response is an empty JSON object. This action requires the `https://www.googleapis.com/auth/ediscovery` OAuth scope. Removing the hold may lead to data purging if no other holds or rules apply.\n"]]
