google_api_vault v0.4.0 API Reference
Modules
API calls for all endpoints tagged Matters
.
Handle Tesla connections for GoogleApi.Vault.V1.
Helper functions for deserializing responses into models.
Accounts to search
A status detailing the status of each account creation, and the HeldAccount, if successful.
Add a list of accounts to a hold.
Response for batch create held accounts.
Add an account with the permission specified. The role cannot be owner. If an account already has a role in the matter, it will be overwritten.
Close a matter by ID.
Response to a CloseMatterRequest.
An export file on cloud storage
Export sink for cloud storage files.
Corpus specific queries.
The options for Drive export.
Drive search advanced options
A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); } The JSON representation for `Empty` is empty JSON object `{}`.
An export
Export advanced options
Stats of an export.
The options for groups export.
The options for hangouts chat export.
Accounts to search
Hangouts chat search advanced options
An account being held in a particular hold. This structure is immutable. This can be either a single user or a google group, depending on the corpus.
Query options for Drive holds.
Query options for group holds.
Query options for hangouts chat holds.
Query options for mail holds.
A organizational unit being held in a particular hold. This structure is immutable.
Represents a hold within Vault. A hold restricts purging of artifacts based on the combination of the query and accounts restrictions. A hold can be configured to either apply to an explicitly configured set of accounts, or can be applied to all members of an organizational unit.
The holds for a matter.
Returns a list of held accounts for a hold.
The holds for a matter.
Provides the list of matters.
Definition of the response for method ListSaveQuery.
The options for mail export.
Mail search advanced options
Represents a matter.
Currently each matter only has one owner, and all others are collaborators. When an account is purged, its corresponding MatterPermission resources cease to exist.
Org Unit to search
A query definition relevant for search & export.
Remove a list of accounts from a hold.
Response for batch delete held accounts.
Remove an account as a matter collaborator.
Reopen a matter by ID.
Response to a ReopenMatterRequest.
Definition of the saved query.
The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. The error model is designed to be: - Simple to use and understand for most users - Flexible enough to meet unexpected needs # Overview The `Status` message contains three pieces of data: error code, error message, and error details. The error code should be an enum value of google.rpc.Code, but it may accept additional error codes if needed. The error message should be a developer-facing English message that helps developers understand and resolve the error. If a localized user-facing error message is needed, put the localized message in the error details or localize it in the client. The optional error details may contain arbitrary information about the error. There is a predefined set of error detail types in the package `google.rpc` that can be used for common error conditions. # Language mapping The `Status` message is the logical representation of the error model, but it is not necessarily the actual wire format. When the `Status` message is exposed in different client libraries and different wire protocols, it can be mapped differently. For example, it will likely be mapped to some exceptions in Java, but more likely mapped to some error codes in C. # Other uses The error model and the `Status` message can be used in a variety of environments, either with or without APIs, to provide a consistent developer experience across different environments. Example uses of this error model include: - Partial errors. If a service needs to return partial errors to the client, it may embed the `Status` in the normal response to indicate the partial errors. - Workflow errors. A typical workflow has multiple steps. Each step may have a `Status` message for error reporting. - Batch operations. If a client uses batch request and batch response, the `Status` message should be used directly inside batch response, one for each error sub-response. - Asynchronous operations. If an API call embeds asynchronous operation results in its response, the status of those operations should be represented directly using the `Status` message. - Logging. If some API errors are stored in logs, the message `Status` could be used directly after any stripping needed for security/privacy reasons.
Team Drives to search
Undelete a matter by ID.
User's information.
Helper functions for building Tesla requests.