List Quota Definitions
const url = 'https://example.com/network/v1/quota-definitions';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/network/v1/quota-definitionsReturns a paginated list of quota definitions for the network service.
Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”Page Size
Maximum number of quota definitions to return. The service may return fewer than this value. If unspecified, at most 20 definitions 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 ListQuotaDefinitions call.
Provide this to retrieve the subsequent page. When paginating,
all other parameters provided to ListQuotaDefinitions must match
the call that provided the page token.
Filter
AIP-160 filter expression (e.g., “container_type=WORKSPACE”).
Order By
AIP-132 ordering expression, e.g. ‘metric asc’.
Responses
Section titled “ Responses ”OK
ListQuotaDefinitionsResponse
Response message for ListQuotaDefinitions.
Note: This API intentionally omits total_size from list responses.
Keyset pagination does not support efficient total count computation
(COUNT(*) requires a full table scan). Per AIP-158, total_size is optional.
object
Quota Definitions
The list of quota definitions.
QuotaDefinition — metadata describing a quota: what it limits, its unit, type, container scope, applicable dimensions, and platform-wide default. Seeded via Flyway. Each service owns its own quota definitions.
object
Unique identifier for this quota definition.
The human-readable metric identifier following the
<service>/<resource>/<measure> convention (e.g., “network/vpc/count”).
A human-readable display name (e.g., “VPCs per workspace”).
An optional longer explanation of what this quota limits.
The unit of measurement (e.g., “count”, “bytes”, “bytes_per_second”).
The quota type: ALLOCATION (concurrent cap) or RATE (time-windowed).
The taxonomy scope at which this quota is administered (ORGANISATION, WORKSPACE, or GROUP).
Ordered list of applicable dimension names (e.g., [“region”], [“zone”], or [] for global). Quota limits must only use keys from this list.
The platform-wide default limit applied when no explicit QuotaLimit override exists for a given container and dimensions.
Whether administrators can create QuotaLimit overrides for this metric.
For RATE quotas only: the refresh interval as an ISO 8601 duration (e.g., “PT1M”, “PT1H”). Empty for ALLOCATION quotas.
Created Timestamp
When this quota definition was created.
Updated Timestamp
When this quota definition was last updated.
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
{ "quota_definitions": [ {} ], "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" } ]}