Gets the specified hold in Google Vault
A documented Google Vault operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Gets the specified hold.
- GETReads data · matters
vault.googleapis.com/v1/matters/{matterId}/holds/{holdId}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Google Vault operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Google Vault operations
- Creates a matter with the given name and descriptionPOST · changes data
- Creates a saved queryPOST · changes data
- Counts the accounts processed by the specified queryPOST · changes data
- Adds an account as a matter collaboratorPOST · changes data
- Creates a hold in the specified matterPOST · changes data
- Deletes a long-running operationDELETE · changes data
- Creates an exportPOST · changes data
- Starts asynchronous cancellation on a long-running operationPOST · changes data
Questions
- Can HumDay gets the specified hold in Google Vault?
- Yes. This operation is published in Google Vault's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Google Vault account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Google Vault.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Google Vault account.
Where this came from
Read from a published API description for Google Vault at vault.googleapis.com/$discovery/rest?version=v1. The description above is the provider’s own wording, not ours. Last published 2023-04-21.