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

Get Workspace

GET
/taxonomy/v1/organisations/{organisation}/workspaces/{id}
curl --request GET \
--url https://example.com/taxonomy/v1/organisations/example/workspaces/example

Returns a workspace by unique ID within an organisation

organisation
required
string

The organisation the workspace belongs to, or ”-” (AIP-159) to read across organisations. Callers using ”-” must have the required permission at a scope covering the resolved workspace (typically WORKSPACE(id) or higher).

id
required
string

The unique identifier of the workspace to retrieve

OK

Media type application/json

Workspace resource: the resource isolation boundary for all platform services

object
id

The unique identifier of the workspace

stringOutput only
organisation_id

The organisation this workspace belongs to

stringOutput only
group_id

Optional group (folder) the workspace is placed in. An IAM binding scoped to that group automatically covers this workspace.

string
name
required

The handle of the workspace, e.g. “prod-eu”. Lowercase letters, digits and hyphens; letter-initial; no adjacent hyphens. Parent-scoped-unique. Used to address the workspace by name or id.

string
display_name

A human-readable label for the workspace, e.g. “Production EU”. Free text in any script. Never used to address the workspace. Optional; defaults to the handle (name) when omitted.

string
create_time

Created Timestamp

The timestamp when the workspace was created

string format: date-time Output only
update_time

Updated Timestamp

Timestamp when the Workspace was last updated

string format: date-time Output only
state

Lifecycle State

This workspace’s own lifecycle state. Changed only through the lifecycle verbs, never by update.

string format: enum Output only
Allowed values: TAXONOMY_RESOURCE_STATE_UNSPECIFIED TAXONOMY_RESOURCE_STATE_ACTIVE TAXONOMY_RESOURCE_STATE_SUSPENDED TAXONOMY_RESOURCE_STATE_ARCHIVED
effective_state

Effective Lifecycle State

The state this workspace actually experiences, accounting for suspension inherited from its group chain or organisation. A workspace whose own state is active reports an effective state of suspended while any ancestor is suspended. An archived workspace always reports archived.

string format: enum Output only
Allowed values: TAXONOMY_RESOURCE_STATE_UNSPECIFIED TAXONOMY_RESOURCE_STATE_ACTIVE TAXONOMY_RESOURCE_STATE_SUSPENDED TAXONOMY_RESOURCE_STATE_ARCHIVED
archive_time

Archived Timestamp

The instant the workspace entered the archived state. Unset unless the workspace is archived.

string format: date-time Output only
state_origin

State Origin

Whether the current state was set directly on this resource or cascaded from an ancestor. Provenance for audit and display.

string format: enum Output only
Allowed values: TAXONOMY_STATE_CHANGE_ORIGIN_UNSPECIFIED TAXONOMY_STATE_CHANGE_ORIGIN_DIRECT TAXONOMY_STATE_CHANGE_ORIGIN_INDIRECT
Example
{
"state": "TAXONOMY_RESOURCE_STATE_UNSPECIFIED",
"effective_state": "TAXONOMY_RESOURCE_STATE_UNSPECIFIED",
"state_origin": "TAXONOMY_STATE_CHANGE_ORIGIN_UNSPECIFIED"
}

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