List Leases
const url = 'https://example.com/vault/v1/workspaces/example/engines/qibdo/leases';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/workspaces/example/engines/qibdo/leasesReturns a paginated list of leases within a workspace.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The workspace whose leases will be listed.
Query Parameters
Section titled “Query Parameters ”The maximum number of leases to return. The service may return fewer than this value. If unspecified, at most 20 leases will be returned. The maximum value is 100; values above 100 will be coerced to 100.
A page token, received from a previous ListQibdoLeases call.
AIP-160 filter expression.
AIP-132 order_by expression, e.g. “issued_at desc”.
Responses
Section titled “ Responses ”OK
Response payload from List Qibdo Leases
Carries the output produced by list qibdo leases.
object
The page of leases.
QibdoLease resource — a workspace-scoped, time-bounded credential lease issued by the Qibdo vault engine. Leases bind ephemeral credentials (database, cloud IAM, SSH OTP, K8s SA tokens) to a principal for a fixed TTL with optional renewal. The credential payload itself is NEVER persisted in the relational database — only the lease metadata.
object
The unique identifier of the lease (UUID).
The workspace this lease belongs to (UUID, weak reference to taxonomy).
The principal (IAM user / service account) the lease was issued to.
Initial time-to-live for the lease.
Maximum total lifetime including renewals — capped by the engine.
Whether the lease can be renewed.
Whether the lease can be revoked early.
Timestamp when the lease was issued.
Timestamp when the lease expires (may be extended by RenewQibdoLease).
Current lifecycle status of the lease.
The engine that produced this lease (database / cloud_aws / cloud_gcp / cloud_azure / ssh / kubernetes).
Engine-specific role identifier the lease was issued against (e.g., the vault
database role name for database leases).
The engine-side lease identifier (e.g., vault lease ID). Used as the prefix key for bulk-revoke operations.
Timestamp when the lease metadata row was created (server-managed).
Timestamp when the lease metadata was last modified (server-managed).
Weak reference to a topology Location — where this resource resides. Defaults to the global location when omitted at creation and is immutable thereafter. Only the global location is available in this release.
Opaque token for the next page; empty when no more results.
Example
{ "leases": [ { "status": "LEASE_STATUS_UNSPECIFIED", "source_type": "LEASE_SOURCE_TYPE_UNSPECIFIED" } ]}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" } ]}