List Operations
const url = 'https://example.com/vault/v1/operations';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/vault/v1/operationsReturns a paginated list of vault operations, optionally filtered by resource type, workspace, principal, or operation type via AIP-160 filter. Platform-admin-only.
Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”Page Size
Maximum number of operations to return. The service may return fewer than this value. If unspecified, at most 20 operations will be returned. The maximum value is 100; values above 100 will be coerced to 100.
Page Token
A page token, received from a previous ListOperations call. Provide this to retrieve the subsequent page. When paginating, all other parameters provided to ListOperations must match the call that provided the page token.
Filter
AIP-160 filter expression (e.g., ‘resource_type=“com.qibdo.cloud.vault:secret”’).
Order By
AIP-132 ordering expression.
Responses
Section titled “ Responses ”OK
List Vault Operations Response
Response message for ListOperations. Per AIP-158, total_size is omitted — keyset pagination does not support efficient total count computation.
object
Operations
The page of vault operations.
Vault Operation
Tracks the result of a vault command (secret, crypto key, lease, certificate authority, certificate, access policy, or vault-level lifecycle action).
object
Operation ID
Unique identifier of the operation.
Workspace ID
The workspace in whose namespace the operation was executed.
Resource ID
ID of the affected resource (nullable for vault-level lifecycle ops such as snapshot).
Resource Type
URN of the affected resource type (e.g., “com.qibdo.cloud.vault:secret”).
Operation Type
The action performed (CREATE, ROTATE, REVOKE, ENCRYPT, …).
Status
The operation status (PENDING, RUNNING, DONE, FAILED).
Insert Time
When the operation was created.
Start Time
When execution started (nullable).
End Time
When execution completed (nullable).
Progress
Progress percentage (0–100).
Warnings
Non-fatal notices emitted during the operation.
Vault Warning
A non-fatal notice emitted by a vault operation. The operation still completed; the warning surfaces unsupported features or capability gaps in the underlying engine.
Warning codes follow the S_SSS_EEE convention:
- Millions digit: service (9 = vault)
- Thousands: group
- Units: specific warning
object
Warning Code
Numeric identifier of the warning type.
Description
Human-readable explanation of what was ignored or degraded.
Next Page Token
A token, which can be sent as page_token to retrieve the next page. If this field is empty, there are no subsequent pages.
Example generated
{ "operations": [ {} ], "next_page_token": "example"}default
Section titled “default ”Default error response
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. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.
object
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
object
The type of the serialized message.
Example generated
{ "code": 1, "message": "example", "details": [ { "@type": "example" } ]}