List Namespaces

GET

/registry/v1/workspaces/{workspace}/engines/qibdo/namespaces

curl --request GET \
  --url https://example.com/registry/v1/workspaces/example/engines/qibdo/namespaces

Returns a page of namespaces in a workspace, filtered by AIP-160 expression and ordered per AIP-132.

Parameters

Path Parameters

workspace

required

string

The unique identifier of the parent workspace

Query Parameters

page_size

integer format: int32

The maximum number of namespaces to return. The service may return fewer than this value. If unspecified, at most 20 namespaces will be returned. The maximum value is 100; values above 100 will be coerced to 100.

page_token

string

A page token, received from a previous ListQibdoNamespaces call.

filter

string

AIP-160 filter expression

order_by

string

AIP-132 order_by expression

Responses

200

OK

Media type application/json

ListQibdoNamespacesResponse

Response message for ListQibdoNamespaces. 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

namespaces

The list of namespaces.

Array<object>

object

id

stringOutput only

workspace_id

stringOutput only

name

required

string

description

string

region_id

required

string

registry_url

stringOutput only

created

string format: date-time Output only

updated

string format: date-time Output only

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.

string

Example ^generated

{
  "namespaces": [
    {
      "name": "example",
      "description": "example",
      "region_id": "example"
    }
  ],
  "next_page_token": "example"
}

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"
    }
  ]
}