Skip to content
qibdo qibdo
v1
API version
  • v1
Theme
Book a demo

Get Quota Limit

GET
/network/v1/quota-definitions/{quota_definition}/limits/{id}
 
curl --request GET \
  --url https://example.com/network/v1/quota-definitions/example/limits/example

Returns a quota limit by unique ID.

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
quota_definition
required
string

The quota definition the limit belongs to.

id
required
string

The unique identifier of the quota limit to retrieve.

Responses

Section titled “ Responses ”

200

Section titled “200 ”

OK

Media type application/json

QuotaLimit — an override of a quota definition’s default limit for a specific container (organisation, workspace, or group) and optional dimensions. Resolution: explicit QuotaLimit > QuotaDefinition.default_limit.

object
id

Unique identifier for this quota limit.

stringOutput only
quota_definition_id

The quota definition this limit overrides.

stringOutput only
container_id
required

The scoped resource (workspace UUID, org UUID, group UUID) this limit applies to.

string
container_type
required

The taxonomy scope type (ORGANISATION, WORKSPACE, or GROUP). Must match the parent quota definition’s container_type.

string
dimensions

Key-value dimension overrides (e.g., {“region”: “us-east-1”}). Empty map means global/unscoped. Keys must be from the parent definition’s dimension_keys list.

object
key
additional properties
string
effective_limit
required

The overridden limit for this container and dimensions.

integer format: int32
created

Created Timestamp

When this quota limit was created.

string format: date-time Output only
updated

Updated Timestamp

When this quota limit was last updated.

string format: date-time Output only
Example generated
{
  "container_id": "example",
  "container_type": "example",
  "dimensions": {
    "additionalProperty": "example"
  },
  "effective_limit": 1
}

default

Section titled “default ”

Default error response

Media type application/json

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
code

The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

integer format: int32
message

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.

string
details

A list of messages that carry the error details. There is a common set of message types for APIs to use.

Array<object>

Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

object
@type

The type of the serialized message.

string
key
additional properties
any
Example generated
{
  "code": 1,
  "message": "example",
  "details": [
    {
      "@type": "example"
    }
  ]
}