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

Parameters

Path Parameters

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

Responses

200

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 display name of the workspace

string

created

Created Timestamp

The timestamp when the workspace was created

string format: date-time Output only

updated

Updated Timestamp

Timestamp when the Workspace was last updated

string format: date-time Output only

Example ^generated

{
  "group_id": "example",
  "name": "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"
    }
  ]
}