List Silences
const url = 'https://example.com/observability/v1/workspaces/example/silences';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/observability/v1/workspaces/example/silencesReturns a paginated list of silences (AIP-160 filter, AIP-132 order_by).
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The workspace whose silences to list.
Query Parameters
Section titled “Query Parameters ”The maximum number of silences to return. The service may return fewer than this value. If unspecified, at most 20 items will be returned. The maximum value is 100; values above 100 will be coerced to 100.
A page token from a previous ListSilences call.
AIP-160 filter expression.
AIP-132 order_by expression, e.g. ‘created desc’.
Responses
Section titled “ Responses ”OK
ListSilencesResponse
Response for ListSilences. Keyset pagination intentionally omits total_size (AIP-158).
object
The list of silences.
A silence is a workspace-scoped suppression window: while active, firing alerts whose labels satisfy the matchers are muted. It carries no engine axis. A silence is created and deleted, never edited.
object
The unique identifier of the silence.
The workspace this silence belongs to. Derived from the {workspace} path segment on create;
reported read-only thereafter.
The label matchers selecting which firing alerts this silence suppresses (at least one).
A single label matcher used to select firing alerts for suppression.
object
The alert label name to match against.
The value to compare the label against (exact, or a regex when is_regex is true).
Whether value is a regular expression rather than an exact match.
Start of the suppression window (inclusive).
End of the suppression window (exclusive); must be after starts_at.
Identifier of the principal who created the silence. Server-stamped from the authenticated caller; read-only (never accepted from the request body, to prevent attribution spoofing).
Free-text reason for the silence.
Timestamp when the silence was created.
Timestamp when the silence was last modified.
A token to retrieve the next page; empty when there are no further pages.
Example generated
{ "silences": [ { "matchers": [ { "label": "example", "value": "example", "is_regex": true } ], "starts_at": "2026-04-15T12:00:00Z", "ends_at": "2026-04-15T12:00:00Z", "comment": "example" } ], "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" } ]}